YuppieScum

None of the beta drivers (up to version 3.75) appear to support TV-Out. Looks like you'll have to wait for the "official release" drivers, some time after 17th February.

I'd doubt that a different release of the OS (Pro, Server, Adv Server, App Server, DataCentre, whatever) would make a difference, as they are all the same binaries - remember the NT4 reg key hack to make WorkStation into Server? Unless the drivers are so crap that they'll only work on Pro... Anyway, IIRC, one of the boot options when you hit F8 at start up is a logged boot - much like Win9x. (I can't say for certain 'cos I haven't rebooted in quite a while). Try booting with this and then read back the log file - it should give you a good idea where things are going wrong... Also, there should be a BIOS setting for disabling any given bit of mobo hardware, serial, parallel, SCSI, IDE, etc . . . ------------------ SuperMicro P6DBS (dual UW-SCSI) BIOS 2.2, 2*Celery 300a @ 450Mhz, 384MB PC100 RAM SCSI-A=4.3Gb+9Gb, SCSI-B=Tosh32x CD-ROM, Yamaha4416 CD-RW, Iomega ZIP100, IDE1=4.3Gb IBM EtherJet 10/100 NIC PCI + Nortel ADSL "modem" CL TNT1 AGP + Quantum3D Voodoo2 SLI PCI SoundBlaster Live PCI (not Value) Win2K build 2195 120-day eval

...and at the end of the day, it doesn't matter. It's all the same code... (with the minor exception of the 120-day timebomb in some versions)

Try "search"ing the forum. It's been mentioned before, but I can't be arsed to find the link for you...

Well, sh1t happens, but as long as everything works now...

Hey, d1ckhead! Maybe you should read the news a bit more often. MS have (about a month ago) stated that no drivers that ship with the OS will support OpenGL. OpenGL support will be provided only in IHV-supplied drivers. Maybe you should try and keep up?

Well, I've got a Voodoo2 SLI and I get 60FPS in UT with dual 300a @ 450Mhz... ------------------ SuperMicro P6DBS (dual UW-SCSI) BIOS 2.2, 2*Celery 300a @ 450Mhz, 384MB PC100 RAM SCSI-A=4.3Gb+9Gb, SCSI-B=Tosh32x CD-ROM, Yamaha4416 CD-RW, Iomega ZIP100, IDE1=4.3Gb IBM EtherJet 10/100 NIC PCI + Nortel ADSL "modem" CL TNT1 AGP + Quantum3D Voodoo2 SLI PCI SoundBlaster Live PCI (not Value) Win2K build 2195 120-day eval

OK, so you "know" your mobo is ACPI compliant, and W2K says it isn't....I'd believe W2K. MS have an ACPI H/W compatibility testing tool. Download that and run it before "claiming" compatibility. Also, given that all enabling ACPI will give you is "hibernation" and auto-powerdown after shutdown - both BFDs - what's the point anyway? ------------------ SuperMicro P6DBS (dual UW-SCSI) BIOS 2.2, 2*Celery 300a @ 450Mhz, 384MB PC100 RAM SCSI-A=4.3Gb+9Gb, SCSI-B=Tosh32x CD-ROM, Yamaha4416 CD-RW, Iomega ZIP100, IDE1=4.3Gb IBM EtherJet 10/100 NIC PCI + Nortel ADSL "modem" CL TNT1 AGP + Quantum3D Voodoo2 SLI PCI SoundBlaster Live PCI (not Value) Win2K build 2195 120-day eval

How did yu "disconnect" the SCSI burner? Did you unplug the cable from the back of the burner, or from the card? I would bet the former, and a dangling, unterminated SCSI cable will cause you problems... Either remove the cable altogether, or plug it back in... ------------------ SuperMicro P6DBS (dual UW-SCSI) BIOS 2.2, 2*Celery 300a @ 450Mhz, 384MB PC100 RAM SCSI-A=4.3Gb+9Gb, SCSI-B=Tosh32x CD-ROM, Yamaha4416 CD-RW, Iomega ZIP100, IDE1=4.3Gb IBM EtherJet 10/100 NIC PCI + Nortel ADSL "modem" CL TNT1 AGP + Quantum3D Voodoo2 SLI PCI SoundBlaster Live PCI (not Value) Win2K build 2195 120-day eval

Amazing. People STILL don't get it. There seems to be some sort of fundamental lack of understanding as to what a swap file actually does! A machine will work BETTER with NO swap file than with a swap file in RAM. Of course putting a swap file on a RAM disk will reduce thrashing. Turning off the swap file will do the same. The whole point about the swap file is to increase the total amount of memory to the OS...how will taking some away be a benefit? Solid State RAM - like there's any other kind? What you actually mean are Solid State Disks - a sh1t load of RAM that presents itself to the OS as a disk drive. These are used generally in mainframes and other legacy I/O intensive environments to speed throughput - mainly because the actual hardware has limits on the addressable memory space. I seriously hope you don't regard yourself as an IT professional - this kind of "thinking outside the box" looks more like "thinking outside the rubber room" and gives us all a bad name... [This message has been edited by YuppieScum (edited 04 February 2000).]

It depends on a couple of things - the disk formats, and the applications. 1. Win9x can't read NTFS. 2. Some apps require a whole load of registry settings. UT, Q3A, FreeSpace + FreeSpace2 can be shared across OS's as they either don't need reg stuff, and will create on execution if needed. Office2K on the other hand won't.

Build 2195 is the final release version of Windows 2000. There are currently no Critical Updates available. The updates are only available as regular downloads.

how many devices have you got plugged into you're phone line? all telephone devices have a "ring equivalence number" or REN assigned to them, and a phone line is rated to the total REN is will support. most lines support a REN of 4, and most devices have a REN of 1, so you can have 4 devices before things (like the phones ringing) break.

The existing Matrox G200/G400 drivers for W2K are bloody awful. I have a 32Mb AGP G400, and it's slower than my TNT1 - not only in 3D but also in 2D. The G400 has been out of it's box exactly three times since I got it last September - once when it arrived, and once each time drivers were released...

Under W2K, each user has their own TEMP directory. The correct entry for both the TEMP and TMP environment variables is %USERPROFILE%\Local Settings\Temp The %USERPROFILE% env variable is set by the OS and usually points to x:\Documents and Settings\Username

Given the Os is gold but the drivers are still beta, I'd say the drivers ned to improve a bit...

Look at the last entry in the knowledge base on their site... It took me a while to find it too...

I'll second that motion - something has gone seriously pear-shaped on that box... Blow it away and start again...

A bit of clarification... 1. In the mobo BIOS for serial port 2, you should be able to change the settings to make it COM3, then adjust the modem to be COM2 - basically the same as you're current setup, but with the modem having an IRQ of it's own, and the "low-throughput" devices sharing. 2. Oh well... 3. 3Com/USR, Diamond and others make PCI modems that are NOT WinModems...shame about the slot though. 4. I've seen them in the junk-mail computer catalogues I keep getting, so I can't point to any one place. However, www.pricewatch.com is a good starting point - just put "USB", "HUB" and "Serial" in the search bar. There are also hubs that have PS2 mouse and keyboard sockets too. Also (just remembered) www.usb.org - search their products section for hubs. Let us know what you decide (and how it works out)... [This message has been edited by YuppieScum (edited 31 January 2000).]

Many people are having difficulty installing W2K onto single drivers connected to this controller - so much so that the way out is to plug it into an ATA33 for the install, then swap it back once the install of W2K and the ATA66 drivers is complete. I can tell you from personal experience that installing NT of any flavour onto a drive controller not recognised natively is a real pain - and only better drivers and/or a BIOS upgrade will help. So the solution is...no solution, until the IHV gets their act together... Unless...is the volume > 16Gb? Another forum member reported problems with a 20Gb vol not booting...

The serial issue really comes down to what the OS regards as "at the same time". W2K is a LOT stricter about what it allows to go on. Win9x users are mainly regarded as home users so the rules are relaxed (so they need to reboot every so often, BFD), where NT (W2K is NT5 after all) is used by businesses - and having to reboot 3 times a day and re-key lost data is not an option. Swings and roundabouts.... Anyway, your options are fourfold... 1. Put the modem on COM2 (all on it's own) and have the UPS share IRQ with the Palm, etc. 2. Assign an IRQ to COM3 - don't share. 3. Get a PCI modem - PCI IRQs can be shared much more effectively. 4. Get a USB hub with serial + parallel ports - one IRQ for all the devices including the printer.

The RealPlayer 7 issue has been documented elsewhere, and is certainly not to do with your motherboard - my aging BX mobo and CL TNT1 exhibit the same problem. Interestingly, the behviour of the above combo is the same as you have experienced with PhotoShop - no BSOD, just blank screen amd requiring a reboot. I expect that this is to do with the beta nature of the TNT drivers - does this happen with the drivers that ship with the OS?

"Hibernation" - part of the ACPI spec - is when a complete snap-shot of the current state of the OS is saved to disk and the whole machine shut down. Then on restart, this image is just re-loaded - instead of having to reboot and the OS do the whole hardware discovery, verification, etc. A restart from hibernation usually only takes around 10 seconds or so - as long as it takes to read a file the size of your RAM from disk... APM - Advanced Power Management - is a facility to control the power consumption of individual subsystems within the PC. For example, the HD can be spun down it it hasn't been accessed for more than x minutes. Such things are controlled in the BIOS of the PC, but the OS needs to be aware that it's going to happen, so it can wait a bit longer before timing out. Both were originally developed with laptop machines in mind - to extend battery life - but found their way into desktops too, mainly to extend the life of components, and to allow geeks to leave a machine on 24*7 without the family complaining about the noise... It's also worth noting that only a subset of APM and none of ACPI is supported for SMP machines, and many "ACPI-compliant" machines are actually not - W2K is far stricter than Win9x. Do a search on APM and ACPI at www.microsoft.com if you need more info. Of course, you could have done that in the first place... ------------------ SuperMicro P6DBS (dual UW-SCSI) BIOS 2.2, 2*Celery 300a @ 450Mhz, 384MB PC100 RAM SCSI-A=4.3Gb+9Gb, SCSI-B=Tosh32x CD-ROM, Yamaha4416 CD-RW, Iomega ZIP100, IDE1=4.3Gb IBM EtherJet 10/100 NIC PCI + Nortel ADSL "modem" CL TNT1 AGP + Quantum3D Voodoo2 SLI PCI SoundBlaster Live PCI (not Value) Win2K build 2195 120-day eval

You don't need NT4 drivers - everything you need is right on the CD. Go to Control Panel, Game Controllers and click Add. Now scoll the list until you get to "Microsoft SideWinder (Auto Detect)". Select that and click OK. See, not all that difficult...

The FAQ on how to install it is quite explicit, so if you follow it and the gods are on your side, it'll work. As you'll have read from all the posts here, most of the time the LiveWare gods are not on your side. The simplest solution - aside from sacrificing your first-born* - is to live without it until Creative actually produce LiveWare2K. *Warning : Do not try this at home. Or anywhere else. [This message has been edited by YuppieScum (edited 31 January 2000).]