Shrink

Then do you know from the experience of others using the hacked Directcd 3 whether or not they lose hibernation? Thanks. ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO!

ThC 129 - will your system hibernate and go into standby mode? ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO!

However, if you have the acpi hal installed you will lose hibernation. 2.5d worked fine for me in Win2k final, but lost hibernation and standby. ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO!

This is a known issue (among many others) with the HPT366 controller. One of the reasons I ditched my BE6. Check the abit newsgroups. ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO!

I know that there are lots of posts concerning directcd in win2k but I have yet heard anyone find packet writing software that works in Windows 2000 pro that works in acpi mode and does not result in losing hibernation. If anyone knows of a solution, aside from waiting for adaptec to release a fixed version of directcd, please let me know. Thanks! Also, I am very surprised that a beta of liveware for win2000 hasn't been leaked! What's this world coming to <g>? ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO!

Windows 2000 is not on your computer if you formatted drive c: (assuming that is really where you installed windows 2000). Your bios can not possibly detect which os you have and the os does not change the bios in any permanent fashion as you are describing. If you are running an smp system then, as Seldzar said, your bios should be reporting that. One more time - if you formatted your system drive, it is PATENTLY IMPOSSIBLE for there to be any remnant of the operating system left. ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO!

All hotkeys work great with version 1.1 of the intellitype software. Good job MS - and all in only a 178kb patch (for those with 1.0 already installed). ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO!

I would be looking at a bios update as a possible solution. You can also check out www.usbworkshop.com as a possible source of info (check out the discussions section there). I have a whole bunch of usb peripherals (including the intellimouse explorer and the MS Keyboard Pro) and they all work better in win2k than in win98. ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO!

Go to a command prompt window and type convert /? and it will tell you all you need to know. ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO!

Lord - My WinTV PCI (I have the dbx stereo & FM model) works great in Win2k. I picked up a WinTV Go and it was a piece of crap but this card is very stable and is well supported (at least compared to the TV Wonder I have) by the manufacturer. ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO!

Yep! They sure did make a big announcement... and it included absolutely nada concerning the TV Wonder. I now have an Hauppauge WinTV PCI - made by a company that properly supports their products. I finally received the version 2 of the software for the TV Wonder and, considering the delay, I thought for sure that there would be win2k support. Hell, practically every other BT8xx TV Card manufacturer has beta win2k drivers. Nope - not ATI. FWIW, I am happy with my WinTV PCI in Win2k final. ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO!

LOL - no problem - I was told that catch-phrase around 13 years ago by a social worker with whom I used to work and have used it in workshops and conferences I have done ever since. I began using it as an email sig around 5 years ago. It is kind of wierd seeing someone else using it <g>. I changed it a bit 'cause I was getting sick of it - it had been just plain "92% of the things we worry about don't happen". Enjoy! ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO!

No comments on DirectX 8 but I see that you have picked up my sig!!! ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO!

Good Karma is coming my way <g>. Run setup again from the cd and after the first reboot when it asks you to press F6 if you have any devices to install, press F5 and it will give you the choice of which HAL to install - choose Advanced Configuration and Power Management PC. Then continue as usual. There is a somewhat more difficult and problematic way of doing this by switching Standard PC to ACPI PC and then copying files manually from the CD, but I would go the setup route. If you just try to change from Standard PC to ACPI PC via device manager you won't be able to reboot your system :-) Good luck. ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO!

... maybe it's the November drivers? That's what I was using.

VooDooD - As I have said in a couple of other threads, with the NT4 liveware and drivers hacked so that they work, my system was benching at 33% of its' normal speed in Winbench '99 (14 vs. 44 cpu marks) and Wintune 98. I removed liveware, changed the hal back to acpi, and reinstalled the wdm sblive drivers and the system was speedy again, not to mention using hibernation. I have a single PIII-500 on a BX chipset mobo. ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO!

... and if all of the above works, benchmark your system to see if there is any degradation in performance, especially cpu performance. I had it installed in mine PIII-500 with 128mb ram on a BX chipset mobo, running with all the features working, and it benched out at 33% of what it should have been based on Winbench CPU mark and Wintune 98 - when I uninstalled the sblive nt4 drivers, reverted back to the wdm drivers and reenabled acpi mode and pci steering, my system was snappier and benched where it should be. For example, with the nt4 drivers and hacks installed, I was getting around 15 cpu marks and it went up to 44 cpu marks when I reverted back, not to mention having hibernation back. At this point I have decided that it just isn't worth it, considering that within 6 weeks something should be released. My advice would be back up your configuration before you reinstall liveware so that you can easily revert back. Good luck :-) ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO!

For the love of Pete! Just reboot into safe mode and take the original woodoo3.dll and copy it into the \winnt\system32 dir and then copy the voodoo3.sys into the \winnt\system32\drivers dir. The reboot and there you have the original 2 files. If you want to lose any remnants of the old one, do a search for 3dfx*.* and delete everything you find below the \winnt subdir. DAMNED DOUBLE POSTS!!! I clicked Submit Now, then I am taken to some advertising website (Planet somethingorother) so I figure I must have pressed the wrong button - I go back, resubmit, and am again forwarded to that website. So much for "Thank You Shrink, your post was received and you are being forwarded...", the only thing missing to make this seem like a warez board now are popups <g>. If you want to know where the .inf's are located, search for *.inf :-) (btw, they are in the winnt\inf subdir - lol) ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO! [This message has been edited by Shrink (edited 08 January 2000).]

For the love of Pete! Just reboot into safe mode and take the original woodoo3.dll and copy it into the \winnt\system32 dir and then copy the voodoo3.sys into the \winnt\system32\drivers dir. The reboot and there you have the original 2 files. If you want to lose any remnants of the old one, do a search for 3dfx*.* and delete everything you find below the \winnt subdir. If you want to know where the .inf's are located, search for *.inf :-) (btw, they are in the winnt\inf subdir - lol) ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO!

How about hztool? Search for it at www.winfiles.com. By the way, why the importance of 160 over 120? BTW, did you try using a win9x monitor definition file for your monitor? ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO!

Using the beta win2000 drivers, select the multimedia video controller and install it via device manager using the "have disk" method. Rather than selecting Hauppauge WinTV Video, select just plain Hauppauge WinTV. Then install the dowloadable program updates - don't install anything from the cd just in case it is older than the web versions. I installed and am running WinTV2000 & WinTV32, in addition to Radion and IR. I have not figured out how to get video capture to work and I would suggest you not try to install it until there is a fix posted by someone else. This will leave you with a Multimedia Controller, unbound to anything, in the device manager - that is okay - everthing works fine without it. Good luck! ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO!

Thanks Matt - however I have TV working just great with the WinTV2000/32 software. I have my remote and the radio app working as well. However, the only thing that is not working is the video capture:-( If you, or anyone else who has a wintv, has this working please let me know how you did it. Thanks again. ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO!

AFAIK, the only cards that have semifunctional drivers for win2k are from Avermedia and Hauppauge - your card may be Express TV, made by a company which I think is of the same name and who's website at http://www.comp-express.com is no longer available (not a good sign). Good luck :-) ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO!

You will need to seek out the card's manufacturer for support. What TV Card is it? ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO!

I don't know of anyone who got theirs to work and I removed mine on Friday and purchased an Hauppauge WinTV PCI to replace it. I have absolutely no faith in ATI to release drivers that will be win2k compatible. To date they have never even released NT4 drivers. I have emailed them twice and only received the bottled reply about not supporting beta software but not answering the question as to whether they even plan on supporting the TV Wonder in win2k. I was in your boat and tried installing drivers from other cards (Avermedia, and Hauppauge to mention two of them) using the bt878 chipset, however they had different tuners and the drivers did not work for any purpose. I even tried to hack the .inf from the version 2 multimedia centre (found at www.lightspeed2000.com ) to no avail, in addition to trying the wdm drivers from that archive. Nothing worked and I gave up hope. I wish you all the best - when it works it is a very cool card but I found too many bugs. The only thing I miss is video desktop - everything else (plus an FM tuner - big deal) is matched by the WinTV, as well as (most importantly) a company that is supporting its' users with drivers and updates. Rant over <g>. Shrink ------------------ Shrink 92% of the things we worry about don't happen - but the other 8% DO! [This message has been edited by Shrink (edited 03 January 2000).] [This message has been edited by Shrink (edited 03 January 2000).]