lordlee

it doesn't show up there...it shows a, c, d, e, f, h, i....I want to get rid of the "invisible g:" drive....

I don't mean uninstalling using device manager, but I am looking for the method to properly remove a hardware device and all associated drivers in XP. I remember that w/ Win2K there is a control applet called "Unplug or Uninstall Devices", but this functionality doesn't seem to be in WinXP anymore. What's troubling me specifically was that I have a removeable drive that I can't uninstall (becuase I don't have it anymore, so it doesn't show up in the Device Manager), and it's occupying a driver letter...doh Thanks for your help!

Question for you W2K experts: I currently have a W98SE (C + W2K Pro dual boot (D setup but my Win98SE is kind of screwed-up (I installed too much junk there). I am thinking about converting W98SE to WinME for C: by killing c:\windows and do a clean WinME install. But I am afraid that doing so will kill the boot sector in the process and I won't be able to boot W2K at all! Can anyone shed some light on this topic? Thanks!

Just bought a Radeon, but found out its performance (at least in Q3a) sucks compared to Geforce 2 GTS... Anyone has any tips for optimizing Radeon in games (the dvd/2d performance is VERY nice, and that's why I bought it)...

My viewsonic 790 makes a loud and long delay every time there is drastic screen mode change (say from 100hz 1024.x786 to 60hz 640x480). It was never a problem for me before DirectX8 because i could either use a refresh rate program (Nvresfix) or Dxdiag's override function to set every to 100hz or 85hz. BUT, when i moved to DirectX 8, the problem becomes unbearable as every screen change, say from starting Diablo 2 to actually getting in a game I have to go through about 10 of these delays. Quake3 is better but still maybe 5 of these just to get in a game. Does anyone else who has run into a similar problem and/or have a solution? BTW, I use Nividia Geforce 2 GTS (the same problem w/ Geforce 256) and its only a problem w/ W2k + DX8 (I have no problem w/ the same setup w/ dual boot W98SE + DX8)....

My viewsonic 790 makes a loud and long delay every time there is drastic screen mode change (say from 100hz 1024.x786 to 60hz 640x480). It was never a problem for me before DirectX8 because i could either use a refresh rate program (Nvresfix) or Dxdiag's override function to set every to 100hz. BUT, when i moved to DirectX 8, the problem becomes unbearable as every screen change, say from starting Diablo 2 to actually getting in a game I have to go through about 10 of these delays. Quake3 is better but still maybe 5 of these just to get in a game. Does anyone else who has run into a similar problem and/or have a solution? BTW, I use Nividia Geforce 2 GTS (the same problem w/ Geforce 256) and its only a problem w/ W2k + DX8 (I have no problem w/ the same setup w/ dual boot W98SE + DX8)....

Like many others, I am a frustrated user of WinTV and W2K VFW viewers (any wintv screen resize freeze my pc). After doing some research on this forum, I decided to install the WDM driver (on www.cyberlink.com.tw) after DirectX8 comes out. Now it's out, I was wondering if any brave soul has done it, and could share the exprience?

Hi guys. I just recently installed a SB Live! Xgamer to replace my Vortex2 card in my bp6 dual box running W2K Pro retail running the latest driver from creative labs. I have noticed that after about 10 minutes of running either a game or WinAmp, the sound will just die (and leaving a low humming on). Or worse, some games will just crash the system). Now I remember that I read in this forum before that some people were having problems w/ SB Live! and W2k in general. Is this problem common among people? Is there a solution for this instability? I don't have any problem (and have SPDIF working too) if I dual boot to Win98SE...

Another interesting thing (it's news to me)..after I flashed to QQ final...MPS 1.4 works fine w/ USB bridge, but gives me 128 IRQs -- now I dont' have any shared IRQs...is that normal?

I have had a really weird USB issue that I have always suspected to be H/W BP6 defect, until I heard that my brother who was also running a BP6 dual celery w2k config had a similar (but not the same issue). I am running the QQ Final bios, and the PCI/USB bridge works fine w/ MPS 1.4. However, I have a MSFT Natural Keyboard Pro 2port USB hub that will sometimes show up as a unknown USB device in W2K AND in Win98. Then it will mysteriously change back to a "generic hub" in the device manger, and stay in that state for a week, then boom, it becomes an "unknown usb device" and stay there for a while, then repeat. I couldn't find the trigger for the life of me Even weirder yet, the upper USB port on board seems to work worse... Now, I do have a Diamond Fireport that shares IRQ 10 w/ the USB controller (but it doesn't generate any conflict, and my SCSI devices work perfectly)...but after I flashed to QQ final, I have 128 IRQs (is that normal?) and no shared IRQs.... Now, any expert BP6 user can share some insight on this little problem that I have (anyone else?) Thanks!

Like many of us,I am still looking for a solution to eliminate all the unstability (random hard lockups, sometimes in Q3)on my W2K w/ BP6 dual celery. One variable that I wasn't sure was the MPS setting in the BP6 BIOS. Does anyone know for a fact what the difference is? Unlike some people, when I use the MPS 1.4 and QQ BIOS (haven't tried the final yet), USB doesn't work. But it SEEMED that 1.4 improved stability... Anyone cares to shed some light on this mystery (at least to me)?

Here was the detailed answers sent to me from AcidSpray...it really helped! To be clear, there are a few > things you need to have ACPI work: > > 1) the latest (QQ beta) bios flashed > 2) the latest 1.231(?) UDMA66 beta drivers installed or on floppy > 3) MPS set to 1.4 in bios > 4) bios set up corretly for ACPI (ACPI enabled, PM disbaled, etc) > > Now, there are two routes you cantake to get a working system from here... > > Route A: Still going for ACPI > 1) You must have the above conditions met, particularly have the latest > UDMA66 beta drivers on floppy and ready to go. > 2) Start the computer, put your windows2000 cdrom in, get into bios and set > it up to boot from cd (cdrom first in boot order). You are going to > reinstall windows over itself (all you files will still be intact, you will > just have to re-apply and windows updates you performed, and reinstall any > drivers that were not resident on the windows CD). > 3) When prompted, hit F6 and also hit F5. You will get a menu to select > computer type...select ACPI multiprocessor. A bit after, you will be > prompted for your UDMA66 drivers...make sure to install the newest betas. > 4) Select install windows2000, not repair...it will then detect windows 2000 > is already on your system and you should get another option to repair the > installation. Repair it, windows will refresh/reinstall all of its > files...leaving all your previously installed files intact. > 5) If everything is in order, Windows2000 will boot up properly under ACPI. > > Route B: Forget the ACPI crap > 1) If you are going to go this route, I would suggest going back to NJ bios, > no sense in running a beta if you don't need it. > 2) I wouldn't go with the beta UDMA drivers on this path either, just the > previous Windows 2000 compatible drivers will be fine. > 3) Start the computer, put your windows2000 cdrom in, get into bios and set > it up to boot from cd (cdrom first in boot order). You are going to > reinstall windows over itself (all you files will still be intact, you will > just have to re-apply and windows updates you performed, and reinstall any > drivers that were not resident on the windows CD). > 4) Hit F6 when prompted and install the non-beta (older) Win2k compatible > UDMA66 drivers. > 4) Select install windows2000, not repair...it will then detect windows 2000 > is already on your system and you should get a second option to repair the > installation. Repair it, windows will refresh/reinstall all of its > files...leaving all your previously installed files intact. > 5) If everything is in order, Windows2000 will boot up properly under MPS. > > > Good luck! All I can say is that my method of switching to ACPI worked for > me, your mileage may vary. It is important to mention however than while > ACPI is nice, it did nothing aboutn the random lockups. In fact, I have > clean installed Windows 2000 twice since then, and am still having the > problem. Once was to get back to MPS and make sure ACPI wasn't the problem. > The other was...hmmm...I forget...chasing another possible crash issue, > that didn't pan out... > > -AciD > > >

THanks for all help guys! I really appreciate it...I did a "reinstall" and "repair" and everything is back to normal. Thanks for all the info and help..especially AcidSpray who sent me a long and detailed email that really helped me out...I will post his detailed answer when I boot my Win98 partiion...

HELP!!!! I was attempting to fix random lockups on my W2K Pro retail running in MPS with a BP6 board. I installed the latest QQ BIOS and updated my computer driver from MPS Computer to ACPI MPS Computer (and enable ACPI/disable APM in the BIOS). Then my W2K will NOT boot up and will only give me a BSOD!!! HELP.. How can I revert to my original configuration (MPS computer)? Or help solve the BSOD problem? PLEASE....I am BEGGING you....I tried the Safe mode, and it still gave a BSOD...PLEASE

I just fixed the problem last night by installing NETBEUI protocol on my win98 box and W2K box. I also found out that if I installed IPX and enable NetBIOS support for IPX, it also works. Thanks for all the help guys I also have a related question: I am using a proxy server to share the Internet among the nodes on the LAN (TCP/IP and NETBEUI). HOwever, the performance of the proxy seems worse running on W2K (I could dual boot the W2K using W98)....any guesses or similar experience. I am running aVirt Gateway by the way. Thanks again all