[RogueSpear]

I ran across something a little wierd today testing out the driver packs. My install would not even get to the blue text mode portion. I was getting an error stating that the txtsetup.sif was missing or corrupt and a status message of 14.

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!

[Caramel]

I am unsure where exactly svcpack.inf gets run... where does it ???

btw i don't actually run svcpack.inf at all

[evilvoice]

ok, the way it goes is this
t-39
install devices
install network
install windows
install components
runonceex
svcpack.inf (t-13)
cmdlines.txt (t-12)
i believe there is a t-9 but I dunno how to invoke it or anything
save settings
clear tempfiles
reboot
login
runonceex
guirunonce
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.

[Bâshrat the Sneaky]

@RogueSpear: Are you sure you properly patched your txtsetup.sif in that case? Because that's the only possible reason why the ultra.sys file error showed up!

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

[RogueSpear]

Yea I ran everything proper. I read over all of the threads related to this top, read all of your instructions twice just to make sure. Am I the only one who has this EOF character? I checked out my txtsetup file thats right on my corp SP2 CD and its in there too.

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.

[Thauzar]

@evilvoice anyway I run runonceex from cmdlines .txt so there is no conflict since it is ran after svcpack.inf should have run (but doesn't )

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?

[Bâshrat the Sneaky]

@Thauzar: in fact I wanted to say something like you too: this topic shouldn't be a 'DriverPack-topic' or something, but the questions DO concern Pyron's method:

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

[Thauzar]

@bashrat this error seems to be linked with you driver pack if I understand a bit of what you were talking about (method 2 etc.)cause I don't think pyron's setup is restarting over and over again, or this has just never happened here since p.1. But since you seem to know a lot in drivers integration and stuff, have any idea why svcpack is not working with pyron's method? that would help

[Bâshrat the Sneaky]

I have no clue, Thauzar, if I had *any* idea, I would have posted it a while ago, I've been tracking this topic!

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!

[fc.dobriy]

Excuse I badly I speak on english, do not pay attention to mistakes. To me has liked DriverPacks and I want to make loading DVD a disk with him (and with other operational systems). Whether it is necessary for me after integration DriverPacks
Anew to create Boot Folder?

[Bâshrat the Sneaky]

Are you saying this?


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!

[fc.dobriy]

Sorry

[Thauzar]

@evilvoice

Everything works great man!!! thank you so much. Thus I now have a valid alternative to svcpack.inf And for Ryan's driver pack, well it's sad but I was not planning on using them anyway.

[yanghaijun]

When i start the windows 2000 setup from CDROM, the presetup.cmd and the svcpack.inf can works verywell, but when i boot to dos, and run setup from dos command line, like this : winnt /s:e:\i386, the svcpack.inf can't works, why?

I want to install the cat File manually, what should i do?

[Muschi]

You can also start presetup.cmd @T13 Setup Stage.

winnt.sif

[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))))"

presetup.cmd

REM Hide cmd Window
@cmdow @ /HID

[ile5]

Hi
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)

svcpack_fix.zip include:

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.

iLE

Attached File(s)

•  svcpack_fix3.zip (49.77K)
  Number of downloads: 151

This post has been edited by ile5: 07 November 2004 - 08:58 PM

[Thauzar]

@ile5 TESTED AND PROVEN WORKING!!! Wow man, thanks a lot, appart from doing another setup.exe (which I don't have the competences for), I really tried everything else to make it work. I knew something that stupid was preventing svcpack.inf from running, and you found it out in one day! GREAT! Now if pyron can replace the 1st post with the new files, this thread can now be recommanded as a proven method that works perfectly

[evilvoice]

only problem is -newsetup is now hardcoded...instead of being able to pass commands through presetup.cmd

[ile5]

Command Parameter(s) is not hardcoded anymore !
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.

svcpack_fix3.zip include:

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.)


iLE

Attached File(s)

•  svcpack_fix3.zip (49.77K)
  Number of downloads: 211

This post has been edited by ile5: 04 November 2004 - 06:17 PM

[jquintino]

this fix is only for 2k?