Login to Account Create an Account
SOLVED: drivers from CD
Posted 20 October 2004 - 08:02 PM
Even though I was only half awake at the time, I quickly noticed that there is some sort of end of file character. It looks like a box. Well it was right where the txtsetup file used to end. So I did a cut/paste to put it at the end and still got the error. Next step, put the original txtsetup in there and sure enough it fired up.
The install did eventually die later saying it couldn't find ultra.sys... so back to troubleshooting.
I'm thinking that maybe I need to take the driver pack entries and merge them under the original sections. BTW I did try to delete the EOF character all together, but that also gave me the error message.
EDIT: OK, I don't know if this is factual or not, but I theorized that doing a cut/paste on the EOF character might somehow change it since it's a special character. So I cut/paste the driver pack entries to move them to above the EOF character and sure enough it worked. Also the error regarding ultra.sys has disappeared. Whew!
Posted 20 October 2004 - 09:00 PM
btw i don't actually run svcpack.inf at all
Posted 20 October 2004 - 11:29 PM
i believe there is a t-9 but I dunno how to invoke it or anything
desktop (this is if you dont include a restart command in guirunonce or runonceex)
I believe that is it I might be a little off as far as installing windows and installing components may be done at the same time, and I might have missed one or 2 things, but this is how setup.exe works...Ive watched it about 30 times with runonceex executing before svcpack.inf...now, the reason it doesnt execute for most people is because it isnt going to be beneficial to them...the whole reason this argument started is because I asked if thauzar was setting the runonceex keys before or after setup.exe %* was run...if it is before, I believe that it will execute too soon and may mess something up. but having it in presetup.cmd to execute after setup.exe %* runs would be fine, and therefore would get executed on first boot.
Posted 21 October 2004 - 04:47 AM
It's being removed by the Patch.cmd, that's being called from RUN_ME_Method_2.cmd.
So I think the problem lies there, are you sure you ran everything correctly?
Bâshrat the Sneaky
Posted 21 October 2004 - 06:25 AM
Once I did get the setup to go on its merry way, it eventually hung at T-33, right at the end of device detection (using method 1). Using method 2, setup keeps on restarting from a blue gui screen that appears like when you do checkdsk.
The Ultra.sys problem went away, and to be honest I never investigated it too carefully, so that could have been something on my part.
Well its a fresh day now, so I'm off to see what I may have screwed up (in both methods).
EDIT: OK, from what I can you must have a carraige return before and after the EOF character otherwise you get the corrupt or missing error. Now I'm getting the error again that setup can't find ultra.sys. I looked in the txtsetup.sif file and it seems that there is another device that goes by the moniker of ultra and uses a file called ultra.sys. Does this seem right?
EDIT2: It looks like XP already comes with a Promise Ultra IDE driver, which I assume is older. Going to try and strip references to it out of txtsetup.inf.
FINAL EDIT: That seemed to do the trick.
Posted 22 October 2004 - 07:28 AM
To all others, seriously, am I missing something out, what are those methods and why do I feel like i'm sudently in "bashrat the sneaky's driverpack help" thread? Don't you have your own thread instead of talking about things that do not concern at all pyron's drivers integration? Pyron's method is clean and simple and works perfectly apart from svcpack.inf not running... so why all those questions by carmel and other about drivers pack and stuff? Can they at least help us get pyron's method running?
Posted 22 October 2004 - 09:46 AM
setup is being restarted... ==> in a loop, when using Pyron's method
Doesn't this seem an error concerning Pyron's method to you? So it's quite logical to post it in this topic...
But still I'd like to ask everyone to post ANY question concerning my DriverPacks to post it in a DriverPack topic!
Voilà! That's said!
Bashrat the Sneaky
Posted 22 October 2004 - 05:05 PM
Posted 23 October 2004 - 09:13 AM
However, now I'll start investigating this problem too... But personnally I think it depends on a VERY minor difference between Windows XP versions. Why? Because:
1. it seems this happens with several language versions of Win XP
2. there is absolutely nothing wrong with what you guys are doing
As I said, when I know something, I'll let you know!
Posted 23 October 2004 - 12:29 PM
Anew to create Boot Folder?
Posted 23 October 2004 - 12:47 PM
I think he wants to say this:
Excuse me for my bad English, don't pay attention to my mistakes.
I like the DriverPacks and I want them to load from a DVD with several OSes.
Should I create a new boot folder after integrating the DriverPacks?
If this is what you wanted to say, please copy/paste it in one of the DriverPack topics, this topic only concerns a METHOD, not the DriverPacks!
Posted 23 October 2004 - 01:15 PM
Posted 25 October 2004 - 09:03 AM
Posted 31 October 2004 - 08:55 AM
I want to install the cat File manually, what should i do?
Posted 02 November 2004 - 08:59 AM
[GuiUnattended] DetachedProgram = ".\system32\cmd.exe" Arguments="/C START /MIN FOR %I IN (D: E: F: G: H:) DO (IF EXIST %I\$OEM$\Setup\Presetup.CMD (%I\$OEM$\Setup\Presetup.CMD) ELSE (FOR /D %J IN (%I\*) DO (IF EXIST %J\$OEM$\Setup\Presetup.CMD (%J\$OEM$\Setup\Presetup.CMD))))"
REM Hide cmd Window @cmdow @ /HID
Posted 02 November 2004 - 06:16 PM
I think i found (after one day digging) what is Problem with "svcpack won't run" in Pyron's method.
OPENED "presetup.cmd" window (hide or not) is main TroubleMaker.
Obviously windows "setup.exe" don't like "*.cmd" window opened in back.
For testing i made setup.exe (in Delphi) with next process:
1. Open "presetup.cmd" and wait for close.
--- In "presetup.cmd" above "Setup.exe" is renamed to "setupold.exe".
--- "Setuporg.exe" is renamed to "setup.exe".
--- Other stuff....
--- Exit "presetup.cmd".
2. Open original "setup.exe -newsetup" ex. "Setuporg.exe" and wait for close.
I tested this file and every time svcpack run normaly.
I don't know how to parameter passing to original "setup.exe" so i put default " -newsetup"
Pyron's method is fantastic, simple and multipurpose and this problem stop my almost finish unattended CD.
I also use Bâshrat the Sneaky's Method_2 for lan & sound drivers which also use this Pyron's method.
@Pyron maybe you change your "setup.exe" and test this method. (maybe i am totaly wrong)
1. setup.ex_ ---------- Normal version - hidden "presetup.cmd" window.
2. setup_dbg.ex_ ---- Debug version - open "presetup.cmd" window.(If you want use this version rename file in "setup.ex_")
3. presetup.cmd ------ I slightly change this file at the end.
Good luck and sorry for bad english.
Edited by ile5, 07 November 2004 - 08:58 PM.
Posted 03 November 2004 - 08:33 AM
Posted 03 November 2004 - 09:56 AM
Posted 03 November 2004 - 01:20 PM
In the new version command parameter(s) pass to the Original setup.exe.
This version is more error verbose in pre setup stage.
Feel free to test this version and post any problem.
1. setup.ex_ ----------- Normal version - hidden "presetup.cmd" window.
2. setup_dbg.ex_ ---- Debug version - opened "presetup.cmd" window.
--------------------------- (If you want to use this version rename file in "setup.ex_")
3. presetup.cmd ------ IMPORTANT - I slightly change this file at the end.
--------------------------- (Delete line "start /WAIT setup.exe %*" in your "presetup.cmd" it is not needed anymore.)
Edited by ile5, 04 November 2004 - 06:17 PM.
Posted 07 November 2004 - 09:31 PM
Posted 08 November 2004 - 06:14 AM
there is a problem and i dont now here?
Posted 16 November 2004 - 07:46 AM
I tried to use your svcpack_fix3.zip in my UA XP CD together with
RyanVM Windows XP SP2 Update Pack: 04-Nov-2004 EDIT: 1.0.3
Bâshrat the Sneaky's DriverPacks Method 2
- DriverPacks BASE - version: 4.10.2
- DriverPack LAN - version: 4.10.3
- DriverPack MassStorage - version: 4.10
- DriverPack Sound - topic - version: 4.10.1
By the way @Bâshrat the Sneaky
in your presetup.cmd (contained in Driver BasePack) the /F parameter is missing here:
REM | Reset DriverPolicy |
reg add "HKCU\Software\Microsoft\Driver Signing" /v Policy /t REG_DWORD /d 1 /F
reg add "HKCU\Software\Policies\Microsoft\Windows NT\Driver Signing" /v BehaviorOnFailedVerify /t REG_DWORD /d 1 /F
reg add "HKLM\Software\Microsoft\Driver Signing" /v Policy /t REG_BINARY /d 01 /F
Otherwise setup displayed and sits at a blue background forever!
Because the "Reg add" command waits for a "y" input (you can't see this in the batch)
I get the following error messages:
1. "Pesetup.cmd" file is missing ! Try to continue normal setup ?
2. setupORG.exe file is missing, Setup Abort!
But your presetup.cmd is still there in the i386 folder of the UA XP CD
(see message screens)
Any tip ???
Thanks in advance
Posted 16 November 2004 - 12:46 PM
Not only for win 2k!
this fix is only for 2k?
1. This is not my method just a "setup.exe" (Pyron's method).
2. I don't know in your case is it windows setup begin and then restart at t-39 or
setup not even begin.
For test try to put this three files in the same directory:
("SetupORG.exe" is renamed original windows "setup.exe")
Edit presetup.cmd and leave only this:
if exist setup.exe ren setup.exe setupold.exe if exist setupORG.exe ren setupORG.exe setup.exe exit
If "windows Xp Setup" window is pop up with "Please go to Control Panel..."
everything is fine because setup is started without parameter.
Check your "Txtsetup.sif" in i386 folder
. . . [SourceDisksFiles] setupORG.exe = 1,,,,,,,2,0,0 ; must exist presetup.cmd = 1,,,,,,,2,0,0 ; must exist . . .
3.setup.ex_, setupORG.exe, presetup.cmd - must be in i386 folder on your xp cd.
Posted 17 November 2004 - 12:15 PM
Thank you for the detailed guide! It works now!
I did not notice the this before !
[SourceDisksFiles] setupORG.exe = 1,,,,,,,2,0,0; must exist presetup.cmd = 1,,,,,,,2,0,0; must exist . .
There is another error message in presetup.cmd
(see my attached file)
But i will find it by my self
Good to have your setup_dbg.ex_ Debug version - open "presetup.cmd"
Thank for your help.
Posted 18 November 2004 - 06:50 AM
I come a small step further, I could solve the problem
"Windows cannot find 'e:\OEM\bin\WatchDriverSigningPolicy.exe'
In your prestup.cmd included in svcpack_fix3.zip there is the following line:
REM +=======================================================+ REM | Enable installation of unsigned drivers | REM |-------------------------------------------------------| start %CDDRIVE%\OEM\bin\WatchDriverSigningPolicy.exe REM +=======================================================+
The "start" Command ??? I removed it now setup continues here.
Now the SetDevicePath.exe could not be found. (see image)
But the file is still the on CD-ROM in \OEM\bin !
I cannot understand it ???
For assistance I would be grateful
Thanks in advance
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users