YuppieScum

The FTP site address for registered beta testers is ftp://ntbeta.microsoft.com

No you won't. I install to an IDE HD from a SCSI CD-ROM all the time. You might want to answer the other questions though...

I use EasyCD4 and WinCDR3.7d under Win2K build 2195 with no problem whatsoever - both my CD-ROM and CD-RW are SCSI...

IIRC, RC2 won't boot to an ATA/66 drive during setup. Put the drive on ATA/33, install then move it back to the ATA/66 afterwards...

win2kbox.8m.com - as metioned in many other messages...

For Q3A use /cg_draw3dicons 0 /vid_restart and restart. If you look closly, you'l see that the screen continues to update, but only in the area immediately around the skull icon at the bottom of the screen! This fixes it. Don't know about UT - are you overclocking the TNT? Using D3D or OpenGL? The OpenGL driver that shipped with 3.52 is the last one that worked reasonably - check the other messages for what to do...

Go to http://win2kbox.8m.com and get the latest TNT drivers. Also, don't overclock the vid-card while etsting, and don't o/c the CPU to anything unusual (115Mhz, etc) as this will also o/c the PCI and AGP bus (on most mobos) which causes BIG problems.

Sounds like a bad driver. Most PCI cards can have a single IRQ shared between them. I suspect something dodgy in a driver is not expecting that... Are you using all native W2K drivers, or are some NT4? Try playing with the BIOS to hard-allocate IRQs to each PCI device, and see what happens. Oh, and upgrade to 2195 too

Ok, lets see if I've got this straight. You've tried removing the "odd" drive h/w, so all you have left is an IDE drive on a regular IDE primary channel, a CD on the regular IDE second channel. You kick off the OS install, it copies files to the HD and reboots into text mode setup. When does it report inaccessible boot device? How large is the IDE drive? Have you tried re-partitioning the drive in the text-mode setup? Have you upgraded the mobo BIOS to the latest version? [This message has been edited by YuppieScum (edited 22 December 1999).]

I did replace the old SETUPREG.HIV with the new one, and the setup still tells me it's a 120-day eval copy - contrary to reports seen here and elsewhere. I'll try installing anyway, but given the current behaviour is not what I was led to expect . . . Oh, and while we're talking credits, how about some props for spotting the eval notice?

What OS build? What driver revision? What overclocking - CPU and vid-card?

Don't know any mobo's off-hand, but http://www.tyan.com have a good rep - hit their site, then hit http://www.pricewatch.com Also, in general it's a bad thing to o/c such that AGP/PCI busses run at greater than 66/33Mhz - which is what happens with odd FSBs and no correction in BIOS. It's usually what causes crashes when playing games - no a CPU failure at all, but a vid-card/bus failure.

Someone in another thread pointed to a copy of the FAQ in the last few days - it's probably worth a look. Drop me a line if you don't find it, and I'll put one together. Oh, and the "setupreg.hiv time-bomb crack" didn't work, so excuse me if I don't bow... [This message has been edited by YuppieScum (edited 22 December 1999).]

That properties page should also tell you what mode it's actually using. I get "Ultra DMA Mode" with my P6DBS...

Given the drivers are quite old, and the ZIP name ends in "_rc2", I think I'll pass...

Go to Control Panel, Admin Tools, Computer Management, Device Manager, IDE etc Controllers, Primary IDE Channel, then hit the Advanced Settings tab. You should see the options there . . .

To make an NT CD bootable, use CDR-Win (shareware) and follow the FAQ at www.win2k.net

I'd recommend getting a dual Slot 1 rather than Socket370 mobo. It is far more likely that you'll get a slocket adapter that will support flip-chips than you will for socket370->flipchip - in fact I think Iwill already have one out. Also the existing slockets for regular Celerons work a treat - I have 2 in my SuperMicro P6DBS with 300a's @ 450.

This question has been answered several times - at least twice by me - already. 1. No "native" drivers will have options to compromise stability under W2K. 2. Use PowerStrip.

Check the FAQ at www.win2k.net - it has the complete blurb as well as the needed boot block. Also, you'll need a copy of CDRWin3.7e or later.

In what way did they not work? BSOD? And what are you using to test them? I'm currently running 2195 with the 3.65 drivers, and Q3A rocks. However, OpenGL is slightly broken for some stuff, and so, after installing 3.64/5 you have to replace the nvoglnt.dll in system32 with the one from 3.52.

BeOS doesn't "auto-multithread". The threading model is completely pervasive throughout the OS and drivers, and the OS itself was designed with this in mind, which is why it handles SMP better. You can't have the OS take a single-threaded app and multi-thread it. It can't happen.

Byron - Good point. It used to be that the HCL would point out instances of "restricted functionallity", but this was in the days of an HCL in HLP file format In theory (always a good disclaimer) a WDM USB driver should install on both 98 and W2K - although for some pre-release W2K the driver needed to be re-compiled. On the other hand, many non-WDM USB drivers still have 16-bit cores - my CL WebCam2 is one such. Also, if the IHVs create WDM drivers only, they're cutting off the entire Win95 user-base. So the cost choice for the IHV is Develop 2 drivers WDM/non-WDM and get 100% of users. Develop 1 driver and get 90%. This may not be completely coherent given the lateness of the hour - maybe i'll edit it tomorrow.

ByronT covered most of the points I intended to raise (thanks!). I normally wouldn't bother justifying myself, but it's 3:52AM and I can't sleep, so... Quote: probably dont even have 2k and/or a live I've been seriously using W2K since around build 2031 as part of the official beta program. I also run Win9x, RedHat 6.1, and BeOS 4.5.2 (just for laughs). I pre-ordered my SBLive (a real one, not a "value"), so I've had it about as long as they've been out. I've also had just about every other SB card since the SB16. In fact, I spent some time with their techs in Shrewsbury (England) to determine why this card wouldn't work with what was the fastest machine around at the time, a 486/33. (It turned out to be "noise" from the CPU - a few extra smoothing caps fixed it.) Quote: so leave it to someone who does to not be a dick and help out. cause if you had some "STUPID QUESTION" id still answer it with a striaght response It looks to me like you got a straight response - completely, 100% factually accurate in an easy-to-read format, and with a bandwidth-conserving brevity. Nor was your question "stupid", just one that has been asked and answered at least a dozen times during the last few weeks. Just because you don't like the answer is no reason to attack the answerer. Oh, and just for completeness, I did some research on the SBLive/Value + S/PDIF question. It took almost 50 seconds to come up with this image, showing the location of the relavent connector. The implementation is left as an exercise for the student. http://support.soundblaster.com/specs/audio/live/images/ct4670.gif [This message has been edited by YuppieScum (edited 17 December 1999).]

Yeah, you'd think people would at least read the FAQ, or the install info, even if they can't be bothered to search the message base . . .