Palos

What makes you think that there weren't any idiots around on ARPANET as well? Military/ govt. ****s up as well, but it takes them decades to admit it, whereas here on this bulletin board we have a pretty open discussion as i can see...

Visiting CeBIT 2 weeks ago, i have found out the folowing: - ALI is aware of this problem and they will post drivers as soon as they're finished on their website...pretty cheesy answer! - More encouraging responses came from Gigabyte (I have a GA5-AX Rev4 mobo - Ali Alladin V chipset): they said the problem is due to the voltage supply unit on the mobo that provides current to the AGP bus. They showed me a small object next to the AGP bus saying that if it's getting too hot and you notice that the system crashes frequently, you should place a cooling fan (!?) on it... they have been testing this problem for a long time now, and are aware of the real problem that the Alladin V chipset has. They will also post any fixes/drivers on their website as soon as they figure it out! So for all of us with an Alladin V + TNT combo, tough luck with W2K, or switch to Win9x!! All of you who wanna buy a Socket7 mobo and a TNT, DO NOT even think about Alladin V... (dammit, why didn't I do this myself earlier )

Server, Adv.server, whatever...couple of $ more This is not the point i was trying to make, anyways. I work as a Network Admin. in a small company and my boss decided to upgrade from Office 95 to Office 2000 and now our propietary database is ****ed...it was a bad move.

Just came back from CeBIT and I was told by Powerquest representatives that they have a patch in the works due for release sometime in April... Conclusion: do not convert all your partitions to NTFS if you have the slightest thought of going back to W9x (or dual booting).

EXACTLY, run under W2K? But why the hell do i want to use floppies, isn't it kinda old-fashioned, and a pain in the ass (esp.with PM5). I never used floppies under NT or 9x, just ran the program from a nice GUI and everything...

I think the only way for you to get back to FAT32 is to wipe out and reformat in FAT32.(the official M$ way). This is why: - If you don't have a FAT partition already, then you're busted, because a normal DOS/Win9x boot disk will boot allright, but it won't recongnize your NTFS partition(uou won't be able to run the DOS .exe's of PMagic like this or in W2K safemode w/command prompt). - Win2K doesn't allow you to make a SIMPLE boot disk, you have to make the whole gang of 3 startup floppies... I'm telling you because I wanted to get rid of W2K and reinstall Win98 (because of TNT2 driver troubles), and I found myself with a single NTFS partition to wipe. I saved my docs and stuff on CDR and I went ahead and savagely dismembered the NTFS beast.

I think you need to give us a bit more details than "i have a 27Gb HDD and then i put an old 8 Gb back in..." Tell me: - you are using both drives now? - did you have a letter (D) assigned to a network drive BEFORE you plugged in the new drive? - Are you using the "logon and restore network connections" option? Give it a bit of effort when explaining your problem in the future

Well, I guess he should be fired anyways for purchasing Win2K Adv.Server without checking for backward compatibility ! -------------------------------- What really pisses me off is that Powerquest does not have a patch for PartitionMagic 5.0 for W2K (yet!). I was in CeBIT Hannover last weekend and I talked to the zombies at Powerquest's stand and they told me they have a patch in the works, due for release late April...go figure!!!

Well, choose one: 1 - Buy other software (WinOnCD 3.7 Power Edition, works ok with W2k). 2 - Fire the IT manager, cos only a dumbass would buy a piece of software for a company without doing research beforehand to see if it's compatible with W2K. Actually you should check if you have the right ASPI layer drivers for W2K (check adaptec.com). Any questions?

I cannot seem to change the OpenGL represh rate, stuck at 60 Hz. I couldn't find a proper key in the registry either... Any ideas??

did anybody try this with a TNT2 ?? I get freakin BSODs everytime i try to access DX or OGL mode, with any drivers > 3.66

Your system is probably set to reboot automatically after a BSOD. You can uncheck that in (rightclick) Mycomputer, advanced, startup and recovery. I had this problem too after i enabled ACPI and APM, i got an IRQ_NOT_LESS_OR _EQUAL or something like that in a nice B(lue)SOD... Right now i have all disabled and my power button is set as instant off in BIOS, therefore i still need to power off manually after shutdown.

Try the following: - Disable APM (adv.power management) - display settings-> screensaver-> power - Disable APM in your BIOS as well, there is a whole section dedicated to APM. Disable everything... As a conclusion your system should shutdown fine, but you will need to manually power off (you might have an "instant-off" option in the BIOS). ------------------------------- Note that monitor/hdd shutdown is still available even after you've done the steps above...just enable the timer from the "power" tab... Tell us how it went...

I would say 192 MB would be enough...i have 128 right now, with an average of 60 MB free. Some applications LOVE not to release the memory soon after they close down (Netscape is a good example) so i have to kill the task manually...

Yea, kind of...i have an Alladin V and a TNT2 (non ultra). The only drivers working for me are the detonator 3.66, the Elsa W2K beta (december 99 build, not the new ones based on det.3.76 !) and the ones currently in use from www.joytech.com I'm getting pretty fed up with Nvidia, they can't seem to get their s*** together for a damn stable piece of code (the sad part is most manufacturers use Nvidia builds for their own drivers...) DAMMIT!

Same problem here, same freaking error message as well. What motherboard you have (chipset) and CPU? I have an Alladin V and a K6-2 with a TNT2 (non-ultra). Here's what you can do: 1 - Try the Nvidia detonators from the lowest build up (3.6x - 3.7x). I'm saying this because only 3.66 worked for me 2 - Try the generic drivers at www.joytech.com, they work for me now and I have AGP support as well checked. Tell us how it goes...

Same configuration here... It runs pretty smooth, although i had some problems with my TNT2. It looks like i fixed them, found some generic drivers at: http://www.joytech.com/support/support_all.htm and AGP support is enabled and working, no more dumb BSODs...in my case, i think the problem is the chipset (alladin V) gfx (TNT2) combo... On the other hand, i wouldn't mind 64 MB more (192 total)!! 256 is a bit too much for what i'm doing, and there is no dramatic performance increase from 192.

For all of you who have problems with TNT/TNT2 and your system crashes with any detonators above 3.6x, try this link below: http://www.joytech.com/support/support_all.htm Those are the first drivers that show AGP as enabled and do not give me a BSOD (K_MODE exception in NV4_DISP.DLL). My system is a K6-2 @ 450 on an ALI Alladin V MoBo, 128 SDRAM, Elsa Erazor III, W2K Pro. Tell me how those drivers work out for y'all ! Cheers!

As i said in an earlier post, i get a freaking BSOD: KMODE exception handling or something IN module NV4_DISP.DLL...nice and big, white on blue!! ANY IDEAS,.....anyone???

I didn't tweak my BIOS at all...the system boots up fine, display works fine, but whenever i try to test OpenGL or DirectX, it gives me the BSOD (with any Nvidia build newer than 3.66).

I must say my excitement died down extremly fast when i noticed the same damn symptoms as i had with ALL detonators except 3.66 ! (ie - they give me a BSOD!). I run w2k pro (2195) and an ELSA Erazor III. The only drivers that didn't crash (both OGL and DX) are the older ELSA beta drivers (build 198 - December '99) and the detonators 3.66!! WHAT THE HELL IS GOING ON????????? My OpenGL test is a Winamp plugin and for DirectX I use the 'test directdraw' in DXDIAG... Please, please,help !!!! ------------------------------ AMD K6-2 @ 450 MHz (no o'c) Gigabyte GA5-AX Rev4 with F3 bios Ali Alladin V Chipset 128 MB SDram SCSI2 CDR ELSA Erazor III AGP 2x

yes, i did install as administrator...by the way, the AGP support in DXDIAG is grayed out and disabled using the drivers that work! Any others show AGP as enabled but crash. I tried disabling it but same thing happened. BSOD!!!! Go figure...stupid ELSA won't release any stable proper drivers until 24th Feb. when w2k is released in Germany! I talked with tech support and they told me they'll come with control panel applet and all...wait and see!! Also i couldn't find any AGP patches/miniports for AlladinV for w2k...they all work ONLY for Win9x...what a piece of crap

Hi there! I have an ELSA Erazor III (TNT2) card and i run W2k Pro(2195). I'm using the latest (beta!) drivers from ELSA but i'm wondering if i could use the NVIDIA Detonators (3.68 i think) for NT4.0? Did anyone try it already? Also, what would be the best driver (even older build) to run (from Elsa or Nvidia)... Thanks!