Jump to content

Unattended Secret: Reducing Size Of Source


 Share

Recommended Posts


Hmm.... I'm working with this CD (trying to get Office 2003 on here - no shrinkage, just 7-zip the full Admin install), but I'm noticing that there are times when the copying of the files at the text setup screen just seems to hang... no errors, just a seemingly unnecessary pause. Once it goes on to the graphical install screen there's no problem.

:wacko:

I'll try re-creating the reduced source.

Link to comment
Share on other sites

  • 2 weeks later...
  • 2 months later...
  • 4 months later...

Hi there!

The error: "CDBOOT: Coudn't find NTLDR" allways apear. I've read the post over and over again and done the instructions over and over again and the result is the same...

Does anyone knows how to fix this?

SOLVED: I was using a modifyed source :P

André Casal

Edited by andregcasal
Link to comment
Share on other sites

  • 2 weeks later...
Hi

you can put all file and folder in

C:\$WIN_NT$.~BT

to

C:\$WIN_NT$.~LS\i386

and delete this files

C:\$WIN_NT$.~LS\i386\migrate.inf

C:\$WIN_NT$.~LS\i386\disk101

C:\$WIN_NT$.~LS\i386\disk102

C:\$WIN_NT$.~LS\i386\disk103

C:\$WIN_NT$.~LS\i386\disk104

C:\$WIN_NT$.~LS\i386\BOOTSECT.dat

C:\$WIN_NT$.~LS\i386\winnt.sif "replace this one with ur own file"

and replace the orignal folder "i386" with this one and burn it without editing boot.bin and setupldr.bin

:hello:

edit:

copy BOOTFIX.bin from old "i386" to the new one ( to avoid setup loop )

this method has been working beautifully for me

Link to comment
Share on other sites

  • 2 weeks later...

Hi there! Is there any way to use this method for multi boot DVDs?

I've tryed but didn't worked.

I've changed both txtsetup.sif (boot and install folder) to reflect the new location of the installation files, but it doesn't seem to work.

It seems some file(s) inside the I386 folder try to access I386 as if it where in the DVD root.

My setup:

DVD\

DVD\XPP1\ - boot folder

DVD\ROOT\XPP1\I386\ - install files folder

As you can see I386 isn't in the root of the DVD. Is there a way around this?

Both my txtsetup.sif have this:

SetupSourcePath = "\ROOT\XPP1\"

Any help would be great! Thanks :)

Link to comment
Share on other sites

  • 4 weeks later...
  • 2 years later...

This method works beautifully.I agree with you.

But the problem is that you don't get the increase in speed if you copy all files in the boot folder into the i386 folder.

If you keep the boot files in a separate folder you get a boost in the speed.

Hi

you can put all file and folder in

C:\$WIN_NT$.~BT

to

C:\$WIN_NT$.~LS\i386

and delete this files

C:\$WIN_NT$.~LS\i386\migrate.inf

C:\$WIN_NT$.~LS\i386\disk101

C:\$WIN_NT$.~LS\i386\disk102

C:\$WIN_NT$.~LS\i386\disk103

C:\$WIN_NT$.~LS\i386\disk104

C:\$WIN_NT$.~LS\i386\BOOTSECT.dat

C:\$WIN_NT$.~LS\i386\winnt.sif "replace this one with ur own file"

and replace the orignal folder "i386" with this one and burn it without editing boot.bin and setupldr.bin

:hello:

edit:

copy BOOTFIX.bin from old "i386" to the new one ( to avoid setup loop )

this method has been working beautifully for me

Link to comment
Share on other sites

I'm following this for xp x64 with sp2 slippy, and it's quite evil, hehe (and no, picture isnt faked).

Thank you so much, im so reading/loving your unattended stuff. Kick a**! :wub:

post-91607-1218118312_thumb.png

Snapshot after having copying $WIN_NT$.~LS and renaming it to Install, as guide says, before any other changes.

Note: Saved 122MB with this process on amd64&i386 folders. SP2 US.

update: I find it more or less impossible to know for sure what i386 or maybe its amd64 entries to replace with BOOT etc. in the setupldr.bin file. there are 7 entries with i386, and 8 or 9 with amd64.

edit: i found out what to replace according to a 32bit version of same file, but process still leaves me with booting problems, incorrect NTLDR.

update2: I think i have figured it out now, lol, Need 2 files to be able to install: WIN51AP and win51ap.SP2. There's also Win51 file, but windows will install happily without it. At least thats what my short tests tell me in vmware.

Edited by TranceEnergy
Link to comment
Share on other sites

  • 2 weeks later...

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.


×
×
  • Create New...