Skip to content
View in the app

A better way to browse. Learn more.
MSFN

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Windows XP Professional x64 SP2 in Multiboot DVD

Gremo
in Multi-Boot CD/DVDs

Featured Replies

Hi, i'm trying to integrate Windows XP Professional x64 SP2 into my AIO DVD with various XP version already working.

So what i do:

I get $WIN_NT$.~BT and $WIN_NT$.~LS folders with this command running XP Professional x64 virtual machine:

D:\AMD64\WINNT32.EXE /noreboot

Delete:

\$WIN_NT$.~BT\BOOTSECT.DAT
\$WIN_NT$.~BT\migrate.inf
\$WIN_NT$.~BT\winnt.sif
\$WIN_NT$.~LS\SIZE.SIF

Rename/move:

\$WIN_NT$.~BT\ ---> ROOT\PRO1
\$WIN_NT$.~LS\I386 ---> ROOT\I386
\$WIN_NT$.~LS\AMD64 --->ROOT\AMD64

Copy:

win51 ---> ROOT\
win51ap ---> ROOT\
win51ap.sp2 ---> ROOT\

Hex edit:

ROOT\PRO1\setupldr.bin
hex address: 0x2060 from "74 03" to "EB 1A"

Final DVD layout:

AMD64
I386
PRO1
win51
win51ap
win51ap.sp2

All works fine. Boot and installation OK.

BUT i want to move AMD64 and I386 folders inside ROOT\Source. Editing PRO1\setupldr.bin didn't do the trick. No luck with PRO1\txtsetup.sif SetupSourcePath, like other Windows XP versions. win51, win51ap, win51ap.sp2 copied also to ROOT\Source.

I get "Txtsetup.sif is corrupt error".

Maybe there is an updated tutorial somewhere?

Thanks in advance, sorry for my poor english :)


i'm trying to integrate Windows XP Professional x64 SP2 into my AIO DVD with various XP version already working.

i want to move AMD64 and I386 folders inside ROOT\Source.

Maybe there is an updated tutorial somewhere?

New tutorial here:

Follow flyakite's tutorial and ignore flyakite's tutorial.

Don't use winnt32.exe.

Create a directory .\XP64.

Copy directories \I386 and \AMD64 to .\XP64\.

Create win51* flag files at root and at .\XP64\.

Copy files setupldr.bin, txtsetup.sif and ntdetect.com to \XP64\.

DVD Layout:

.\WIN51

.\WIN51AP

.\WIN51AP.SP2

.\XP64\AMD64\

.\XP64\I386\

.\XP64\WIN51

.\XP64\WIN51AP

.\XP64\WIN51AP.SP2

.\XP64\NTDETECT.COM

.\XP64\SETUPLDR.BIN

.\XP64\TXTSETUP.SIF

Edit setupldr.bin at directory .\XP64\

@echo off
rem multiboot_XP64.cmd - edit XP64 setupldr.bin
rem created by cdob

rem use gsar.exe: Tormod http://home.online.no/~tjaberg/

set setupldr=SETUPLDR.BIN
set char4=XP64

rem checksum: geitonaki http://www.msfn.org/board/index.php?showtopic=58410
gsar.exe -o "-s:x46:xda:x74:x03" "-r:x46:xda:xEB:x1A" %setupldr%

rem adjust \i386\ntdetect.com and AMD64
gsar.exe -o "-s\i386\ntdetect.com" "-r\%char4%\ntdetect.com" %setupldr%
gsar.exe -i -o "-sAMD64:x5C" "-r%char4%:x5C:x00" %setupldr%
gsar.exe -o "-sAMD64:x00" "-r%char4%:x00:x00" %setupldr%

Edit txtsetup.sif, adjust SetupSourcePath and create BootPath:

[SetupData]
SetupSourcePath = "\XP64\"
BootPath = \XP64\AMD64\

BTW:

txtsetup.sif, SetupSourcePath, BootPath does work at XP32 too.

  • Author

I will try it right now! Thanks for helping and for your time :)

  • Author

How should i edit the boot image? replace I386 with?

How should i edit the boot image? replace I386 with?

As for Boot Sector: follow flyakite's tutorial

replace I386 with used 4 char name, remember .\XP64\ directory.

that's replace I386 with XP64

  • 3 months later...

This is a good way but I get the error:

File \XP64\biosinfo.inf could not be loaded.

The error code is 14.

Setup cannot continue. Press any key to exit.

EDIT: Sorry my mistake I did not amend the "SetupSourcePath" in this file:

\XP64\TXTSETUP.SIF

:blushing:

Now it works!

Edited by LeveL

  • 1 month later...

works perfect thanks so much mate you saved me many days work :)

  • 6 months later...
How should i edit the boot image? replace I386 with?

As for Boot Sector: follow flyakite's tutorial

replace I386 with used 4 char name, remember .\XP64\ directory.

that's replace I386 with XP64

This is a little confusing; Gremo calls it Boot Image, you call it Boot Sector. What exactly do you mean here?

Edited by meowing

This is a little confusing; Gremo calls it Boot Image, you call it Boot Sector.

It's the same thing.

It is the "Microsoft Corporation.img" or "Arnes Boot Record" which is the El-Torito no emulation boot image and that is written to the CD bootsector.

Let's say that before being actually burned to CD it is a Boot Image and after it has been burned it is a Boot Sector. ;)

Here:

http://flyakite.msfn.org/xpprosp1.htm

it's called Boot Sector, it's the 2048 bytes long file that ends like this:

pro1dat.gif

jaclaz

  • 2 weeks later... 
set setupldr=SETUPLDR.BIN
set char4=XP64

gsar.exe -o "-s:x46:xda:x74:x03" "-r:x46:xda:xEB:x1A" %setupldr%

gsar.exe -o "-s\i386\ntdetect.com" "-r\%char4%\ntdetect.com" %setupldr%
gsar.exe -i -o "-sAMD64:x5C" "-r%char4%:x5C:x00" %setupldr%
gsar.exe -o "-sAMD64:x00" "-r%char4%:x00:x00" %setupldr%

So are these still valid as the only 4 required changes inside setupldr.bin for XP x64 (SP2+)?

And should this be applied to both copies of setupldr.bin per OS (the one in the original location and the one in the os-root) ?

Is moving ntdetect.com one folder up simply to get the 4char replacement of i386 working, or is there another reason?

If it would be:

"\i386\ntdetect.com" -> "\%char4%\i386\ntdetect.com"

one would not have to move ntdetect.com in the os-root, right?

Thanks!

Edited by meowing

It's the same thing.

It is the "Microsoft Corporation.img" or "Arnes Boot Record" which is the El-Torito no emulation boot image and that is written to the CD bootsector.

it's called Boot Sector, it's the 2048 bytes long file that ends like this:

pro1dat.gif

OK, I was under the impression that XP64 isos don't use this anymore.. Is there an easy way to obtain such image from an official XP64 iso without having to use Isobuster?
So are these still valid as the only 4 required changes inside setupldr.bin for XP x64 (SP2+)?
Yes, this is valid for XP x64 SP2.

What's (SP2+) ?

And should this be applied to both copies of setupldr.bin per OS (the one in the original location and the one in the os-root) ?
Apply this for relocated versions.

There is no need to change setupldr.bin at original location.

However mixing original and relocated versions may get strange results.

Or work without any issue. No idea.

Is moving ntdetect.com one folder up simply to get the 4char replacement of i386 working
Yes, it is.
Is there an easy way to obtain such image from an official XP64 iso without having to use Isobuster?

BBIE - Bart's Boot Image Extractor http://www.nu2.nu/bbie/

spcmdcon.sys contains the boot image too. At offset 0x17F00, size one CD data sector.

What's (SP2+) ?
Just meant an up to date XP x64 image, I have no idea if MS ever updated setupldr.bin post the XP64 SP2 disk release..
Is there an easy way to obtain such image from an official XP64 iso without having to use Isobuster?

BBIE - Bart's Boot Image Extractor http://www.nu2.nu/bbie/

spcmdcon.sys contains the boot image too. At offset 0x17F00, size one CD data sector.

Thanks!

Is replacing all the amd64 entries as in

gsar.exe -i -o "-sAMD64:x5C" "-r%char4%:x5C:x00" %setupldr%
gsar.exe -o "-sAMD64:x00" "-r%char4%:x00:x00" %setupldr%

really safe?

I ask this because of what it says here:

http://www.msfn.org/board/solution-multibo...004-t58410.html

"Do not replace all occurrences of "amd64" since some of them refer to a section of txtsetup.sif"

When I compare the two setupldr.bin files (the one in that post and the one generated by your gsar commands, the one from geitonaki has a lot more amd64 entries left in there..

Still not clear what to replace in setupldr.bin and what to leave as is... Can someone reassure me the gsar script here is correct for XP x64 SP2 setup?

Edited by meowing

Can someone reassure me the gsar script here is correct for XP x64 SP2 setup?
Yes, it is.

Grub4dos is a multi boot loader.

Grub4dos was enhanced recently, 14th Nov 2009: http://nufans.net/grub4dos/tinybit/

Editing in RAM is possible now. Previous editing is not required anymore.

General grub4dos informations: integrated help file

http://grub4dos.sourceforge.net/wiki/index...ub4dos_tutorial

http://diddy.boot-land.net/grub4dos/Grub4dos.htm

Grub4dos can chainload setupldr.bin: no need for a boot sector file.

title Loading XP install - plain /I386/SETUPLDR.BIN
chainloader /I386/SETUPLDR.BIN

title Windows XP PRO 64 SP2 - multi boot 
map --mem /XP64/I386/SETUPLDR.BIN (rd)
#checksum: geitonaki http://www.msfn.org/board/index.php?showtopic=58410
write --offset=0x2060 (rd)+1 \xEB\x1A
#cdob SetupSourcePath="\XP64\"; BootPath=\XP64\AMD64\  
#http://www.msfn.org/board/index.php?s=&showtopic=126480&view=findpost&p=814566
cat --locate="\\i386\\ntdetect" --replace="\\XP64\\ntdetect.com" (rd)+1
cat --locate="amd64\\" --replace="XP64\\\x00" (rd)+1
cat --locate="AMD64\\" --replace="XP64\\\x00" (rd)+1
cat --locate="\\AMD64" --replace="\\XP64\x00" (rd)+1
cat --locate=I386 --replace=XP64 (rd)+1
chainloader (rd)+1
root ()

Create an account or sign in to comment
Go to topic listing

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Configure browser push notifications
Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.