morillo

I propose we bet on jdul's age. I say 10... i'll give 10:1 odds on it, too. daniel

This is one funny thread... The thing that i find most entretaining is to think about how jdulmage's "friend" came up with the brilliant idea of trying this in the first place... "friend": Crap... my games are not working! jdulmage: Hey.. how about we reinstall win2k? "friend": Hmmm, not thats not enough, I say lets try putting DOS in first! jdulmage: How did I not think of this first? Its brilliant! I guess Im only the second best computer student in school... [This message has been edited by morillo (edited 25 March 2000).]

What i would like to know is what is meant by saying that these drivers "must comply with hpt366 bios revision 1.24 or above". There is no such revision... the latest hpt366 bios revision is embedded in the latest qq bios and thats 1.22, isn't it? daniel

Just a word of warning on PM... I have used it since version 2 was out and while it has worked fine most of the time, i have have a number of instances of bad bahaviour.. It seems specially finicky when resizing partions. I have tried resizing partitions a total of four times and all fours times PM has essenatially killed the data on the partition. This has been the case with NTFS and FAT32 partitions. So, just be careful

Well, hibernation is still somewhat of a problem when you use the hpt66 controller... For some reason ABIT has yet to figure out that part. Hopefully when they release the official version of the QQ bios this will get solved too. in the meantime, you just pretty much have to forget about hibernation if you want to use the hpt66 controller. daniel

APM is, as it were, obsolete. You need to have ACPI enabled on your BIOS (and it would probably be a good idea to have MPS 1.4 selected). This change, however, does not take effect "on the fly". In other words you need to, at a minumin, change win2k's kernel to use ACPI. You can do this as was explained in the previous post or you can "upgrade" win2k on itself. That is, choose "install" after you have given it the hpt66 drivers (via F6) and then choose "repair" (as opposed to fresh install). This will re-install the entire system, while keeping your applications intact. Of course you will have to manually re-install any non-digitally signed drivers you might have put on your box (at the very least video drivers). daniel

Hmmm... Im pretty sure that you are using udma, as 12MBps is actually pretty fast. A 7200 Rpm GXP IBM drive will get about that sustained rate. You go above that (say 33 MBps under UTA or 66MBps under UTA/66) only from buffered reads (hence the "max" transfer rate used by manufacturers). Even with a new DiamondMax VL20 (which is 7200rpm) you get only about 15MBps sustained. In fact, the 1000rpm SCSI Cheetah HDDs i use at work barely get to 18Mbps. daniel

Hmmm.... if its not an SMP thing, maybe there is still hope. do you have any ideas on why the setup utility dies?

Let me guess... you have a dual processor system? This is been reported for the past few days. The "fix" soed not work on SMP systems because the stup utility dies without uninstalling anything. Apparently this happens in NT also and creative released a "patch" that was supposed to fit it, but it does not seem to work on SMP systems. I run a BP6 with two OC'd celerons and had the same problem.

I have tried and retried the "fix" thats been circulating, but it does not work on SMP. The source of the problem appears to be the fact that the "SETUP" utility of liveware3 dies without installing anything when you run it on an SMP machine. I have tried using the "patch" that creative provided a while back at various points during the installation of the fix to no avail. does anyone have more info on this?

Has anyone been successful in geeting this to work on 2128? (the "fix" instructions state that you "need" 2151). Also, how about SMP? I had heard that liveware for NT had problems in SMP... daniel

So, whats the point of allowing people to choose various speaker setups (including quadraphonic) and "Digital out only" on the SBlive drivers, when there is only two-speaker analog support? Is somobody out there at microsoft laughing at us?