You won't have a problem. XP will install the drivers for the wireless adapter. Worst case is you'll have to go to Linksys site and download the card driver. Shouldn't have to however.
Right click my computer.
Select the advanced tab at top.
Look for:
"Start up system, system failure and debugging information".
Click settings and make sure "automaticaly restart" is unchecked.
Once you change that setting the next time the box goes down it will give you an error. Once you catch the error post it here.
It is more than likely a driver problem.
That would work well as long as the person doesn't remove the task. To get arround that you could set your self up as admin and then set the user up as a regular user. They couldnt' remove the task then.
Yes they are. They are very good, but, a bit more expensive than others.
You might want to consider an 800Mhz processor. They don't cost much more then what you are getting and they are hyperthreading enabled.
I'll be upgrading to vbulletin rc4 this weekend. I was going to wait until vb3 is final. I decided that it would be an easier upgrade to final from rc4.
I'm not sure how the upgrade will affect the styles. If the styles work the upgrade should be smooth. If they don't the upgrade will take longer.
There should be a way to install something to to shut down the system after x amount of time. I think this would require you to hire a programmer to do this. I haven't hear of anything that could do this being available now however.
The install will alwys load all drivers for any possible hardware config a user might have. There is no option to cut down on what is loaded. They want the installer to be as dumbed down as possible. Load everything so even the average Joe with no comp experience can install the OS.
I don't agree with it being this way. I know if I had an option to load only drivers for the hardware I have it would cut install time in half. There should be a way for experienced users to load the drivers they need. Something like what FreeBSD has. With FreeBSD you create and format the file system and then load the drivers for you hardware. The only thing loaded are those drivers.
Didn't help then right?
I know that AOL will set itself up as default connection if no other connection is found. It really takes over and makes it next to impossible to remove the adapter.
You might want uninstall tcp/ip and AOL. This should remove all the bindings that AOL leaves behind. Then install the other connection first followed by AOL.
During AOL install there is a way to make sure AOL doesn't set itself up as default connection. Keep an eye out for that option.
No bother at all. That's what the forum is for.
I installed AOL after I saw your post. I have a connection for AOL in my Network Connections folder.
I use DSL so this connection binds to the network adapter and shows as disabled until I connect with AOL 9.
I wanted to see the properties of this connection. For some reason when I right click and click properties it doesn't bring up connection proerties like my other 2 network connections do.
You might want to uninstall AOL and then reinstall.
I don't have a SATA drive installed, but I do have a controller integrated on the motherboard.
XP SP2 build 2055 did not recognize it on install. When I did a clean install of SP2 build 2082 I had to hit f6 and load the drivers first. If I had a sata drive I could have installed on it after loading the drivers.
So to answer you question. It supports sata as long as you load the drivers on install.
The AOL adapter isn't interfering. You have to create a new dial up connection.
If you created the new connection and still can't dial in then you might have to remove the AOL stuff.
To do that open network connections and remove it from there.
Ok. Make sure your bios is set to boot from the scsi drives. Also there should be an option in the bios that will enable the box to boot from scsi cards. Check for enable interger_19 interupt or something like it. It should be in advanced option under devices. Enable that option. Set the boot options for scsi after cdrom and once you load the drivers you should be good to go.
If the above option isn't enabled when the OS scans the bus for boot devices it won't see the controller.
Try loading without hitting f6 to install the drivers.
Windows 2000 has built in support for Adaptec and it will load the scsi drivers for your controller.
I've never had to load any scsi drivers for any controller that I've used.
You won't be able to uninstall it with ad/remove programs. You have to use NukePOET. WinPOET adds drivers to the tcp/ip stack that have to removed with NukePOET.
You can download it here:
http://www.aztech.com/pub/WinPoET_Patch/NukePoET.zip
Follow the directions in the doc file in the zip to use it to uninstall.
Here is all you need to know about it:
http://www.carricksolutions.com/raspppoe.php
There is a download link to it on that page also.
Before you change you'll need to remove winPOET.
In your WinPoET directory is a utility called NukePoet, run it to uninstall WinPoET.
Then follow the install directions in the zip to install Raspppoe.