Mistral

If you installed Home networking the way I think you did then this problem should be easily resolved (I hope). Home Networking Wizard, by default, enables the XP firewall whenever installing Peer to Peer Networks that share a hub. To remedy this, do the following: Control Panel > Network Connections Right click on Local Area Connection, select properties. Choose the last tab "Advanced". Then you'll see whether or not your firewall has been enabled. If it has, uncheck it, if it hasn't, then sorry i'm mistaken. Hope it helps. Mistral

OK, before anybody responds with, "its a reset.exe problem", its not. I have not used any method of cracking activation on my installs, I used a 60 day activation key. Problem: I have 2 comps on a home LAN, one running WinMe, the other running a dual boot WinMe/XP(various attempts from RC1 to 2532). Both comps connect to each other by way of my DSL router, which also enables both comps access to the internet. The comps both have the same subnet mask and the same workgroup (192.168.0.1 and 192.168.0.2, workgroup:mshome), and can ping each other. Now, when trying to acces the XP/WinMe shares with the WinMe machine, it connects no problem, nice and fast. On the other hand when I try to connect to the WinMe shares with the XP boot of the XP/WinMe machine, it takes forever to connect, and when it does, any subfolder also takes forever to connect (forever being close to a minute). Sometimes it even crashes out completely. As you can see, this is totally unacceptable for a supposedly business orientated OS. Has anyone else experienced this problem and found a fix for it? BTW, no firewall is enabled on the XP machine and both comps are connecting by way of the TCP/IP protocol. Both machines have the same username with no pass. The only thing I can see that is strange is that the XP login for the WinMe shares seems to try to login as //WinMe/guest even though there is no "guest" account setup on the WinMe machine. I look forward to hearing of any experience anyone has had with this. It is so annoying to have followed an OS since Beta 1, only to find at the last minute M$ have introduced a bug so important as this one. Regards, Mistral ---------------- Specs: XP/WinMe Comp WinMe comp AMD Athlon 1.333MHz PIII 450 256Mb RAM 384Mb RAM HD 40Gb Seagate HD 40Gb Western Digital GeForce 2MX 400 TNT2 M64 Both have Realtek 8139 compatible Network cards 3com OfficeConnect 812 DSL Router

No, I did see that thread, and tried everything suggested in it, still doesn't work. Networking is slow as hell. I hope that someone comes up with a real solution soon.

I have one or two messages appearing in the application event log whenever I boot the machine: Source: WinMgmt "WMI ADAP was unable to load the winspool.drv performance library due to an unknown problem within the library: 0x0" I've only just recently got this one but its recurring. Anyone know what winspool.drv does and is it important? Does it require a re-install of my build 2195, or should I be able to repair it some other way? Any suggestions? The other message that appears, also recurrent, is: Source: Perfctrs "Unable to read IO control information from NBT device." What is an NBT device? I think it has something to do with RAS / DUN / Networking, but it doesn't seem to be affecting anything on my dialup connection. Any suggestions would be greatly appreciated. Regards. Mistral

Try using these drivers from the Primax Europe Website.. http://www.primax.nl/drivers/colorado_epp_36bit/direct9600/nt/p36_ennt.exe I did not install any other software, just used the twain32.exe that came with Win2k (it automatically replaces the ones supplied with the drivers using Protected File Replacement). I still have the original CD that came with the scanner, but its full of rubbish. I always ignore CDs that come with products in favour of finding more up to date fixed versions, on the 'net. Hope it helps.

This is just a tip for those who may or may not have had problems installing McAfee Virusscan 4.03 for NT on Windows 2000. Users may have experienced a hang at bootup, or an unbelievably long bootup time (>6 mins. on a PIII 450Mhz, 128MB RAM) The problem lies in the Alert Manager (one of McAfees new fangleedoodas) trying to load as a service at startup. If you have installed McAfee with this option selected, DISABLE IT NOW and all your problems will be solved. I'm now back to more reasonable bootup times (< 2mins). Man, am I glad to have sorted that one, I was dying with worry for not having a Viruschecker on my machine while on the 'net. By the way the evaluation version is available on any of Tucows' websites, or you can get it from McAfee direct (but you have to fill out a registration form). Hope this helps somebody.

Just downloaded the lates TNT/GeForce 3.69 drivers from http://members.xoom.com/PitGS/Public/Grafik/GeForce/Win2k_3_69.zip installed and, lo and behold, AGP *IS* enabled. Also it seems that they have fixed a problem I was having with jerky screen in Virtual Pool (sound now delays a bit but that could be the hacked LiveWare I have). Anybody else tried these drivers yet? Please post any degrees of success or failure with this latest offering. [This message has been edited by Mistral (edited 14 January 2000).] [This message has been edited by Mistral (edited 14 January 2000).]

I once had the DirectX diagnostics reboot on me using the 3.69 drivers, but when I dis.enabled the Powerstrip tweak for "reclaiming memory automatically", it worked fine. Dunno if you have this tweak or another one similar enabled? If so, disable and see what happens. Hope it helps.

Sorry, 'fraid I cant help much. I have the same scanner, I think (a Network Highscan Professional, which uses Colorado Direct 9600 drivers.). I installed the NT4 drivers and when I tried to access the scanner it came up with a message saying that I should check that EPP/SPP is enabled, right? However, once I rebooted, it worked fine. I suppose you have already rebooted and tried again, huh? Sorry I couldn't help.

Common problem. The setup file for Liveware 3.0 doesn't start automatically after decompression on some setups. Workaround, after the origila setup extracts all the files and then stops, go to your personal temp directory .. (should be something like "?:\Documents and Settings\Myname\Local Settings\Temp\LW3\Audio\English\Setup) Rename the setup.ex_ to setup.exe and run ... that's it. Should install fine now.

The SuperMicro P6DBE comes with the Intel 440BX chipset. Find out more at http://www.supermicro.com Hope this helps.

Sorry, re-read your post. You say your BIOS only allows you to tweak to 112Mhz, maybe a flash upgrade is available from your board manufacturer (although it's unlikely that this will enable any higher FSB speeds, as that is controled by hardware). Sorry 'bout misunderstanding.

It's probably your RAM. If you still have the older PC66 RAM, the best you can expect is an increase in FSB to 112MHz (and that's only in the best cases). If you upgrade your RAM to PC100 or PC133 you will probably be able to tweak it a little higher to say 124Mhz (if you MB supports it) or even higher. But make sure that your PCI, and AGP buses stay within a reasonable limit (best bet is below 40Mhz PCI, and 67-70Mhz AGP.) Hope it helps.

Well Put. GET YOUR FINGER OUT CREATIVE, OR RISK LOSING A FEW VERY IMPORTANT FRIENDS::: get my meaning ..

In dxdiag under "More Help" theres a way of overriding the default DirectX refresh rates. Hope it helps.

As of yesterday, new drivers were available for the G400 on Matrox's site. http://www.matrox.com/mga/drivers/latest_drivers/home.htm Hope it helps.

And where would one get these beta drivers then? I've checked the NAI site, but no joy.

Just like to say thankyou to everyone on this board who have had problems and have helped out with other peoples problems. If it wasn't for this board, (and one or two other sites ... ), I could get as rude, (actually, no, I think I would be worse) and offensive as other, not quite so fortunate, members of this community. Many thanks again, Keep up the good work, PS. Anyone checked out the IRC channel #NTcompatible yet?

Try on Undernet. I tried first on DALNet and there was nobody. A few online now on Undernet

Check to see if your fan has fallen off your processor!! Stupid, I know, but it could happen. It happened once to one of the machines at work, would work fine for around 10 minutes and then hang, tried everything then until I opened the box and found the fan on the floor. Worth a try ...

Oh, and by the way, you don't have to uncheck "Do not map to this device", that just makes it worse. "if it don't work first time, try, try again ..." Believe me, it works. Listening to Iron Maiden right now, sweet.