CUViper
Members-
Content count
1117 -
Joined
-
Last visited
Never
Everything posted by CUViper
-
are you running the latest build of icq2000?
-
Quote: Originally posted by Rudyatek: Thanks Andersony. However I think I didn't make myself too clear, sorry. I have Win98, the first edition, not Win98SE. I don't find any options for Net Sharing in it. How might it be done in this case? If the Win2k machine is the host (i.e. the one with the internet connection) then you don't have to do the net sharing step on the win98. just make sure all the ip's, gateways, etc are set up as andersony said.
-
Sorry... I've only heard of that problem when you're trying to run off of a burnt copy. No offense, I hope.... If you are playing with an original disk, then I don't know what the problem is.
-
I would imagine that the shop you took it to just had the built-in win2k drivers installed, which do not have direct3d acceleration. In order to get 3d acceleration with nvidia cards, you have to update the drivers. After that, it works great!
-
Maybe you should try ICQ2000 instead... that's what I use
-
Take some money down to the store and buy it... that will fix you right up!!
-
Definitely turn DMA on...
-
Glad to hear it.... I just picked one of those up myself. I haven't installed it yet, as I am still waiting for the processor, but now I will make sure to flash the bios! Thanks for the info....
-
To find your uptime just go into the event viewer and check when the event log was started....
-
I don't remember the exact details, but if you press F6 during setup when it waits for third-party drivers, you can force it to use ACPI drivers. Can someone remember the actual file you have to direct it to? Anyway, if you can figure that out, just reinstall windows on top of itself, and you won't lose any of your other software installations. The only thing you will have to do is reinstall any driver updates you have used.
-
Thanks mr_yellow.... your reply was not quite correct, but it pointed me in the right direction. The Reg key in question is in HKEY_CURRENT_USER\Control Panel\Desktop\ the value is the PaintDesktopVersion. I checked it on a machine without tweakui and PaintDesktopVersion was a REG_DWORD value 0. On the machine stuck with it on, it was a REG_SZ (string) value '0'. A string '0' is far different from a DWORD 0. That is why it was set on. To fix it, delete it so that it goes back to the default (off). If you want, as I did, you can recreate the value as a DWORD 0, which is what it should be. This is obviously a bug with TweakUI... apparantly when you check the 'show version on desktop', it changes it to a string rather than a dword. Anyone have contact info so we can tell them about this?
-
If you find the answer, please post it here too... I enabled it using TweakUI just to see what it would look like, and now it won't go off. Anyone??
-
We tried the beta drivers when they first came out, and discovered the problem with the floppy then. So we uninstalled them and went back to the old ones, hoping that they would fix it in the next release. Then just a few days ago we tried the new drivers, and boom.... the floppy still locked up the computer. We followed the install directions to the letter, and it proceded exactly like the readme said it would. Still no good. Has anyone found an address that we could write to Aureal to let them know about this?
-
My friend has been having the exact same problem as you with every version of the drivers... only the built-in sound drivers will let him use the floppy drive. Very strange....
-
here is the link for the drivers that eddie mentioned: ftp://ftp.adaptec.com/pub/BBS/winnt/aspi32.exe
-
Quote: Originally posted by Spastic Computer Guru: T problem there is C:/ and D:/ are 2 partitions, I was actually thinnking of setting D:/ as the primary until 98 is on then setting C back to primary.... To install 98 you'll have to do that (set d: as the primary), but if you switch is back later then 98 will not boot. The only way 98 can boot is if it has some basic files on the primary partition. What you will have to do is set bootstar to make d: the primary when you want to run 98, and make c: the primary when you want to run 2k. If you ever get around to reinstalling, you can make your life easier and put 98 on c: and 2k on d:
-
Actually, here's something i just found that may save you from reinstalling: BootStar http://www.star-tools.com/bootstar/english/ With this program, you could set it up so that when you boot to 2k, it shows your primary partition normally, and when you boot to 98, it shows the other partition as the primary partition. Just something to check out anyway... the author only wants $20 for it. I have a friend that uses it and he says it works great!
-
Yeah, the Win9x installation has to be able to write on the primary partition. I don't think you'll be able to just switch the drives around though (assuming they're separate physical drives). If you did that, you would basically have to reinstall everything to get the paths right, and you said already that you don't want to reinstall. If your two drives are really just two partitions, then you will definitely have to reinstall to get Win9x. I think your only sane option here is to reinstall, doing the Win9x and then Win2k
-
Quote: Originally posted by EddiE314: .....you say: "It can be done...", yea, i know it can, but you can also drive a f*ckin car with your feet, but it might not be a good idea and it might not be the easiest g0dda*ned thing to do! actually, i think driving without your feet would be a lot harder....
-
easy: if you are a MS beta tester, then your cd will say what beta version it is. If you bought it at the store, you have the final version. Assuming of course that you have Win2k legitimately....
-
I read somewhere that if you create a file called ddhelp.exe in the system32 directory, it will fix problems like this. It doesn't matter what is in the file, just that it is there. I haven't tried this myself though...
-
Don't know, I'm an admin on my system and it works just fine....
-
Edit the boot.ini and set timeout=0. This doesn't really get rid of it, but at least you won't ever see it.
-
The 3.81 drivers worked fine for me in games, but most (not all) of my OpenGL screen savers crashed to DrWatson as soon as I ran them. Even the screen savers that ship with Win2k (i.e. 3D FlowerBox) would crash. I went back to 3.78 and everything works fine. Anyone else try this?
-
I followed your directions for getting the bug to occur, and it didn't happen to me.