wurzl100 Posted August 26, 2008 Share Posted August 26, 2008 (edited) Hi community,after 5 days of trying to integrate my VIA SATA driver it works now. I didnt do it by Nlite or Driverpacks because everything went wrong.I saw a file from Microsofts Knowledge Base with which I proceeded and now Windows XP is installing unattended.The Problem I have is the following:Within the DOS based setup, when the files are copied to the harddisk it takes unusually long. For 10 Minutes nothing happens, and in the grey colored bar on the bottom of the screen where usually the copied files are displayed is nothing.After around 10 Minutes Windows is starting to copy the files.After this problem the setup is proceeding normal.When I install it with my CD there is no time Problem.Does anybody know how I could fix this problem ?Thanks in advancewurzl100 Edited August 26, 2008 by wurzl100 Link to comment Share on other sites More sharing options...
g555 Posted August 28, 2008 Share Posted August 28, 2008 Doing nothing (apparently) when you need it to do something is just about as bad as doing unknown stuff all on its own.With SATA, I'm guessing a pretty modern system; but just to cover the bases:CPU?RAM? Link to comment Share on other sites More sharing options...
Dislocated Time Posted August 29, 2008 Share Posted August 29, 2008 I had a few problems like that before.I'm supposing that you added the driver to your winnt.sif.You have to be very careful to read the MS article on this very carefully.You have a number of possibilities here.The media (CD/DVD) that you used for the unattended app might be the problem (scratched, dirty or the drive just doesn't find the media appetizing enough). This happens albeit rather rarely.A second possibility that happens more often is that the operating system might be going through some form of search routine for the correct driver. Also, if the driver supports 1000 different types of drives and it goes through a hardware search, that also might take quite some time. In this case, editing the *.inf file might help.I also get those kinds of problems when Windows is almost finished and starts searching for network hardware.There also might be a bios setup that is affecting your installation.Check all that and you should find a solution. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now