Alanoll

I recently recieved the framedyn.dll error. I resolved it by actually adding the entries to txtsetup.sif and dosnet.inf as RyanVM's website states.

I don't think this has been posted, or if it has, it was a different version. I've seen this before, but now others can as well.

I'm just curious if you read the KB article before actually assuming that it should be added. I don't see Service Pack 2 listed there......

gotta love those simple answers

but .\ should still have the same effect as it gets the path of the working directory which at CMDLINES.TXT is $OEM$. But do try without .\ as Bashrat suggests.

instead....did you happen to try msiexec.exe /i (MSIFILE) /qb ?

will you be defining said %system% somewhere? It does not exist otherwise.

yes, rename to logonui.exe. modifype it. makecab it. replace original and your done. Atleast with what I got out of it, since you don't wanna keep the original (stupid idea, but oh well).

A search would bring up the command line, as this has been posted REPEATEDLY ever since it first came out. And as this is NOT true integration rather just adding the setup file to a script (Batch Script in this case), I'm closing the topic.

BAH! Testcases.... you could have always just created your OWN hole, so you could have some fun......... ....... I dunno, I'm gonna have to go with GM with Sox in Six. Man, good thing I wasn't still with my girlfriend (technically) or else I wouldn't be now. Sox fan here, Yankee fan there.

now the REALLY stupid thing.... If you buy the retail, you don't get the back catalogue (supposedly), even if you buy the $80 Collector's edition. But if you pay $60 on Steam, then you get the entire back catalogue, DOD:Source HL:SOurce and HL2 and CS:C Stupidest idea ever.

Bloody shame about adding files to WFP..... Twas worth a shot, but now I think I can digitally sign drivers.

did you ever consider asking Wraith and telling him you think his server is down?

Or, don't do it all in UltraISO, instead copy it all to the harddrive, then follow same steps, then recreate ISO. I never Understood why people directly manipulate ISO's. THe more you do it, the more the risk of them screwing up.

really is ashame that the old 2003 site was merged with the XP one, but then again I think it was done because THEY ARE THE SAME. Sorry, Just incase someone else comes across this. Sure PARTS are different (like themes and unhardening IE) but the majority can be transfered over exactly.

the key in unattend.txt in I386 does not actually get used by setup. Infact, unattend.txt does not get used by setup, unless YOU TELL IT TO USE IT.

@paul3vanz Again, BABY STEPS. You should have started with JSUT AN XP CD. Not a multiboot or whatever you have. Checked to see if the XP CD worked, before progressing. It's not a hard concept, and you can track where errors go wrong easier. Do you build a house complete it, and then go...."Why isn't the power working?" Do you build a complete computer system, and then go "Why is my processor burning up?"

I dunno, I didn't really find anything new in this pack... True I didn't do it, but I did already know how to manipulate the Component Manager (How do you think I install my kernels? A batch script??), and copy files via INF and all that jazz. Now the REAL trick that me and Ryan and probally others are trying to figure out is how to digitally sign it (for free, or use Microsoft's). I've been able to do as such, but the problem is, without a certificate from a root authority or figuring out a way to silently install the cerficate there with the preinstalled one or find out Microsoft's private keys (which by the way, are extremely large Prime Numbers). Other then that, I've got it figured out.

which is why when testing something new....what do you do? What's that you say.....try EVERYTHING at once? even if you've used the program again, it's always better to take BABY steps. lol. The space should have no problem. If it can't find the file, it's most likely that it's not being copied in hte proper place. It doesn't look on the CD for it. So DOSNET.INF and TXTSETUP.SIF entries are irrelevant at that point (except for the txtsetup.sif line where ti tells it where to copy to, but that's just a single number)

now seriously, don't report any framedyn.dll or autoexec.nt or config.nt errors in this thread. Last I looked, this pack doesn't even come CLOSE to modifying those, and editing the txtsetup.sif file is two lines, so it's SOMETHING ELSE.

oh my.... well glad to know you actuall type /? , unfortunately, this has been around since before SP2. And all it does.... adds the fiels to DOSNET.INF and TXTSETUP.SIF (i think) and then adds it to SVCPACK.INF

first, the lines you displayed WILL NOT START THE INSTALL. lol. but assuming you just did this from memory....alittle more info is needed. What kind of installer does PerfectDisc use? Have you tried searching THEIR site?

@xper Thanks, but already been there It would make sense taht it's a Intel chipset, but I haven't been able to isntall the chipset software.... As for the USB drivers, they're not listed on the page either....

go after the file of the ISO when created and optomized (should make it smaller). That is the size you should concern yourself with.

go after the file of the ISO when created and optomized (should make it smaller). That is the size you should concern yourself with.