Jump to content











Photo
- - - - -

Live xp and BootSDI


  • Please log in to reply
62 replies to this topic

#26 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 14 October 2013 - 12:18 PM

I think, there is some confusion about the actual layout of bee4u USB-Stick.

@bee4u
- Do you try to boot a bootsdi.img, which is located on the USB-stick in folder i386?
- Or do you try to boot a bootsdi.img, which is located in folder i386 in LiveXP_RAM.iso on the USB-stick?

Please be very clear about it! (try: dir /b /s)
At the moment Wonko and cdob work under different assumptions.

:cheers:

#27 bee4u

bee4u

    Frequent Member

  • Advanced user
  • 172 posts
  •  
    United Kingdom

Posted 14 October 2013 - 12:28 PM

@cdob

 

Do you get a "Loading RAMDISK image..." without grub4dos --mem version?
Do you get a "Loading RAMDISK image..." with grub4dos --mem version?

There it is, post the winnt.sif.

Which hardware do you use?
Which desktop and whitch laptop?

Yes ." without grub4dos --mem version , Yes ." with grub4dos --mem version , on real pc Desktop  only with mem and on real Laptop both ways

Winnt.sif : [SetupData]
BootDevice="ramdisk(0)"
BootPath="\i386\System32\"
OsLoadOptions="/fastdetect /minint /rdexportashd /rdimageoffset=32256 /rdpath=\i386\BootSDI.img"

 

Hradware: Desktop :Pentium DualCore E5200  @2.50GHz 1 GB Ram , Laptop Packard Bell  Intel Core i3 380m 4GB DDR3 Ram.

Desktop   windox xp home ,   Laptop windows 7 64 bit home basic

Try 
title LiveXP_RAM
find --set-root --ignore-floppies /LiveXP_RAM.iso
map
/LiveXP_RAM.iso (0xff)
map --hook
root
(0xff)
chainloader /I386/SETUPLDR.BIN

On VM works ok , On real pc Desktop with mem works  but without mem it gives error 25 disk read error , on Laptop it works both ways.

 

@ Wonko the Sane

 

find --set-root /i386/bootsdi.img
chainloader /i386/setupldr.bin
boot

i get error after typing boot command " Setup is inspecting your computer 's hardware configuration... NTDETECT failed .

and it hangs there.

List of files :  usb stick is formatted fat32 it has on the root I386 directory (BOOTSDI.IMG , BOOTSDI.PLN, NTDETECT.COM , SETUPLDR.BIN , PROJECTINFO.INI  )  menu.LST , grldr  file , WINNT.SIF



#28 bee4u

bee4u

    Frequent Member

  • Advanced user
  • 172 posts
  •  
    United Kingdom

Posted 14 October 2013 - 12:34 PM

@MedEvil

 

I think, there is some confusion about the actual layout of bee4u USB-Stick.

@bee4u
- Do you try to boot a bootsdi.img, which is located on the USB-stick in folder i386?
- Or do you try to boot a bootsdi.img, which is located in folder i386 in LiveXP_RAM.iso on the USB-stick?

I try to boot a bootsdi.img, which is located on the USB-stick in folder i386 , and  cdob talks about LiveXP_RAM.iso in which bootsdi.img is located in folder I386 in the iso on the USB-stick only , its differnt topic, no problem with LiveXP_RAM.iso



#29 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13443 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 14 October 2013 - 12:47 PM

@ Wonko the Sane
i get error after typing boot command " Setup is inspecting your computer 's hardware configuration... NTDETECT failed .
and it hangs there.

Good :).
Try copying SETUPLDR.BIN and NTDETECT.COM to the root of the stick, then use:

find --set-root /i386/bootsdi.img
chainloader /setupldr.bin
boot

:cheers:

Wonko



#30 bee4u

bee4u

    Frequent Member

  • Advanced user
  • 172 posts
  •  
    United Kingdom

Posted 14 October 2013 - 12:59 PM

@ Wonko the Sane    got error  "  windows could not  start due to an error while booting from a RAMDISK.

windows failed to open the RAMDISK image.

File BOOTSDI.IMG could not be loaded the error code is 14

setup cannot continue .press any key to exit.



#31 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 14 October 2013 - 01:49 PM

@bee4u
Has anyone ever told you, that you have a very confusing way of giving information?

A.) the location of setupldr/ntdetect does not matter at all, when chainloaded
B.)Winntsif seems wrong.
BootPath="\i386\System32\" there shouldn't be a i386 folder in bootsdi.img, but a minint folder. Please check.

btw. Why do you fiddle with all this by hand and didn't let LiveXp create a bootable USB stick for you?

:cheers:

#32 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 14 October 2013 - 01:54 PM

@Wonko
What for do you have
find --set-root /i386/bootsdi.img
in your configuration?
The root should be the root of the USB-Stick, where the winnt.sif file is.
Which then tells setupldr everything it needs to know.

:cheers:

#33 bee4u

bee4u

    Frequent Member

  • Advanced user
  • 172 posts
  •  
    United Kingdom

Posted 14 October 2013 - 02:08 PM

@MedEvil

 

@bee4u
Has abyone ever told you, that you have a very confusing way of giving information?

well i dont think so and i try to give info to the point .see the post no 1

 

How to boot BOOTSDI.IMG of live xp on usb..?

may be you think in different way... :dubbio:

 

B.)Winntsif seems wrong.
BootPath="\i386\System32\" there shouldn't be a i386 folder in bootsdi.img, but a minint folder. Please check.

btw. Why do you fiddle with all this by hand and didn't let LiveXp create a bootable USB stick for you?

There is no minint folder in in bootsdi.img i checked

yes i created livexp_ram.iso with bootsdi option then taken from ISO folder/ Ram folder  the i386 folder which has  bootsdi.img and other files cuz LiveXp  bootable USB stick is not created gives error... :confused1:

see bootable USB script error pic attached

Attached Thumbnails

  • 1.JPG
  • 2.JPG


#34 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 14 October 2013 - 03:06 PM

Normally Setupldr loads Windows on a CD /ISO from folder i386.
But on HDD / UFD and RamDisk it loads Windows from minint.

:cheers:

#35 bee4u

bee4u

    Frequent Member

  • Advanced user
  • 172 posts
  •  
    United Kingdom

Posted 14 October 2013 - 03:16 PM

But i dont have minint folder in the bootsdi.img.. :confused1: i386 folder  is created by bootsdi script option in livexp..!



#36 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 14 October 2013 - 04:47 PM

Ok. Did some checking and it seems my memory is indeed a bit off, with bootSDI.

Folder i386 in BootSD.img is ok! (Don't know why, but it works. ;))
My Winnt.sif reads: 
[SetupData]
BootDevice="ramdisk(0)"
BootPath="\i386\System32\"
OsLoadOptions="/noguiboot /fastdetect /minint /rdexportashd /rdpath=\i386\BootSDI.img"

Structure:
\projectinfo.ini <-- useless!
\wint.sif
\i386\setupldr.bin
\i386\ntdetect.com
\i386\BootSDI.img
It works just fine this way, though without g4d!

:cheers:

#37 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13443 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 14 October 2013 - 04:48 PM

@Wonko
What for do you have
find --set-root /i386/bootsdi.img
in your configuration?
The root should be the root of the USB-Stick, where the winnt.sif file is.
Which then tells setupldr everything it needs to know.

Well, this way I make sure it roots on the right drive.

 

 

My guess is that there are too many guesses, too little real experience on what that project/build is made and an ongoing mixup of information (mostly mixed up) from bee4u, who is not particularly accurate when reporting (and from too many people posting overlapping information and increasing - involuntarily and with all the best intentions - the mess).

 

For all we know the SETUPLDR.BIN may have been modified (as it should have been, or at least how I used to very often to do) to use \i386\ on *any* media:

http://www.911cd.net...showtopic=17504

 

@bee4u

I suggested you (wrongly)  a WINNT.SIF pointing to /rdpath=BootSDI.img did you had the error 14 with it or with the "right" one with /rdpath=\i386\BootSDI.img?

 

:cheers:

Wonko



#38 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 14 October 2013 - 04:57 PM

Well it has been dead for about 6 years.
So everyone is a bit sketchy on the details. :wheelchair: :lol:

:cheers:

#39 bee4u

bee4u

    Frequent Member

  • Advanced user
  • 172 posts
  •  
    United Kingdom

Posted 14 October 2013 - 04:57 PM

@ Wonko the Sane  i am following your instructions and posting the result as i get form following your instruction.... :dubbio:

any feed back about post  no 30...?



#40 cdob

cdob

    Gold Member

  • Expert
  • 1315 posts

Posted 14 October 2013 - 05:24 PM

Yes[/color] ." without grub4dos --mem version , Yes ." with grub4dos --mem version , on real pc Desktop  only with mem and on real Laptop both ways

Setupldr.bin "Loading RAMDISK image..." print this message, if ram loading a image.
And grub4dos --mem loads the image to ram too.
Hence you use double RAM load. One RAM disk is obsolete.
However, does it works at all machines? Then use RAM load always.
 

Hradware: Desktop :Pentium DualCore E5200  @2.50GHz 1 GB Ram , Laptop Packard Bell  Intel Core i3 380m 4GB DDR3 Ram.

Describe the hardware more detailed. Which Desktop do you use? Which manufacturer, modell, motherboard and BIOS version.
Packard Bell builded more then one laptop, describe the hardware more detailed.
 

without mem it gives error 25 disk read error

Does grub4dos or setupldr.bin print this message?
Which colours do you get on screen?
 
 

I try to[/color] boot a bootsdi.img, which is located on the USB-stick in folder i386 , and  cdob talks about LiveXP_RAM.iso in which bootsdi.img is located in folder I386 in the iso on the USB-stick only , its differnt topic, no problem with LiveXP_RAM.iso

I wonder if hardware limits both approaches?

Ideas:
USB disconnected/reconected at ntdetect.com: use a patched ntdetect.com
size limit BIOS, acccess first part of USB drive only

Which USB drive do you use? Manufacturer, Modell, Size

Which approach do you like to settle?
LiveXP_RAM.iso or single files at USB disk?
Boot LiveXP from USB disk at all machines, the approach is open?

#41 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13443 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 14 October 2013 - 05:27 PM

@ Wonko the Sane  i am following your instructions and posting the result as i get form following your instruction.... :dubbio:

any feed back about post  no 30...?

I thought that my post #37 provided the feedback.

 

Let's forget temporarily about LiveXP (wrong name as it is a PE) and bootSDI (wrong name because it is a RAW image and NOT a SDI).

 

The booting mechanism with the Windows Ramdisk have been correctly posted by Medevil here:

http://reboot.pro/to...otsdi/?p=178378

 

The requisites are rather simple.

There must be a SETUPLDR.BIN and this SETUPLDR.BIN MUST come from SERVER 2003 SP1 (and NOT from *any* other build), as well as NTDETECT.COM and  RAMDISK:SYS (this latter inside the image), see this seemingly unrelated thread:

http://reboot.pro/to...xp-now-working/

http://reboot.pro/to...orking/?p=40232

 

The SETUPLDR.BIN may be renamed to something else, like NTLDR (though I personally strongly discourage this practice) and it may (on the contrary strongly suggested by me) edited to boot from \i386\ on all type of media (posted earlier link). 

There must be a WINNT.SIF.

The contents of the WINNT.SIF need to respect the path of the image.

Normally (but it is very possible that this can be changed) SETUPLDR.BIN, NTDETECT.COM and WINNT.SIF needs to be on ROOT of the boot device (hd like), as well as the actual RAW image, BOOTSDI.IMG.

You need to read attentively these threads:

http://www.911cd.net...topic=10482&hl=

http://www.911cd.net...topic=19333&hl=

 

Then you will have ALL the data needed to perform your experiments, knowing what you are doing.

 

:cheers:

Wonko



#42 bee4u

bee4u

    Frequent Member

  • Advanced user
  • 172 posts
  •  
    United Kingdom

Posted 14 October 2013 - 06:56 PM

 @ Wonko the Sane

 

@bee4u

I suggested you (wrongly)  a WINNT.SIF pointing to /rdpath=BootSDI.img did you had the error 14 with it or with the "right" one with /rdpath=\i386\BootSDI.img?

Yes with WINNT.SIF pointing to /rdpath=BootSDI.img , i had the error 14 with itand  with the "right" one with /rdpath=\i386\BootSDI.img...

WORKING.... :1st: :cheerleader: :1st: :clap: ..THX.. :thumbsup:

when i put BootSDI.img out of i386 folder in the root of usb it too work pointing to /rdpath=BootSDI.img...both way worked.

the error is from wrong path. THE JOB IS DONE..... :clap:

@cdob  BOOTSDI.IMG booted without mem from grub4dos both on desktop and laptop from usb

usb stick is formatted fat32 it has on the root I386 directory (BOOTSDI.IMG , BOOTSDI.PLN, PROJECTINFO.INI )  menu.LST , grldr  file , WINNT.SIF, NTDETECT.COM , SETUPLDR.BIN



#43 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13443 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 14 October 2013 - 07:16 PM

Good :).

Now you can try putting "back" the SETUPLDR.BIN and NTDETECT.COM into the \i386\ directory.

I seem to remember that it won't work :dubbio: (i.e. on hard disk-like media those two files, as well as WINNT.SIF need to be in ROOT, but as said I may well be  wrong about that :unsure:).

You can put the image *anywhere* as long as the right path is WINNT.SIF, of course.

 

:cheers:

Wonko



#44 bee4u

bee4u

    Frequent Member

  • Advanced user
  • 172 posts
  •  
    United Kingdom

Posted 14 October 2013 - 07:24 PM

 @ Wonko the Sane putting "back" the SETUPLDR.BIN and NTDETECT.COM into the \i386\ directory , it didnt work. you are right.

 chainloader /setupldr.bin   error 15: file not found..!



#45 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13443 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 14 October 2013 - 07:38 PM

 @ Wonko the Sane putting "back" the SETUPLDR.BIN and NTDETECT.COM into the \i386\ directory , it didnt work. you are right.

 chainloader /setupldr.bin   error 15: file not found..!

NO, NO, NO, NO! :frusty:

 

If the SETUPLDR:BIN is in in \I386\ OBVIOUSLY is not found in ROOT! 

 

You need to:

chainloader /i386/setupldr.bin

OR, as you have been suggested before, use:

chainloader /

[TAB]

to make use of the grub4dos autocompletion/file listing features.

 

:cheers:

Wonko



#46 bee4u

bee4u

    Frequent Member

  • Advanced user
  • 172 posts
  •  
    United Kingdom

Posted 14 October 2013 - 07:39 PM

@ Wonko the Sane  why this command didnt work just for the sake of knowing.. :rolleyes:

title LiveXP-BOOTSDI
find --set-root /i386/BOOTSDI.IMG
map /I386/BOOTSDI.IMG (hd0)
map --hook
chainloader (hd0,0)/NTLDR



#47 bee4u

bee4u

    Frequent Member

  • Advanced user
  • 172 posts
  •  
    United Kingdom

Posted 14 October 2013 - 07:53 PM

 @ Wonko the Sane  sorry path mistake again....   putting "back" the SETUPLDR.BIN and NTDETECT.COM into the \i386\ directory

and using chainloader /i386/setupldr.bin , i get error after typing boot command " Setup is inspecting your computer 's hardware configuration... NTDETECT failed and it hangs there. same error as post no 27



#48 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13443 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 14 October 2013 - 07:57 PM

@ Wonko the Sane  why this command didnt work just for the sake of knowing.. :rolleyes:

title LiveXP-BOOTSDI
find --set-root /i386/BOOTSDI.IMG
map /I386/BOOTSDI.IMG (hd0)
map --hook
chainloader (hd0,0)/NTLDR

That is NOT a command, it is a set of commands assembled in a menu.lst entry, i.e. exactly what you have been suggested to NOT do because there is no way to know what doesn't work.

In any case, besides the form (assembled in a menu.lst entry, they also make NO sense whatsoever and "didn't work" is not a description of what happened, and even if it was, without knowing the contents of BOOTSDI.IMG it's impossible to know.

I would guess that there is no NTLDR in the root of the BOOTSDI.IMG. :dubbio:

 

 

 

 @ Wonko the Sane  sorry path mistake again....   putting "back" the SETUPLDR.BIN and NTDETECT.COM into the \i386\ directory

and using chainloader /i386/setupldr.bin , i get error after typing boot command " Setup is inspecting your computer 's hardware configuration... NTDETECT failed and it hangs there. same error as post no 27

Yes, then it is confirmed that I remembered right, on hd-like media SETUPLDR.BIN and NTDETECT.COM need to be in root (while on CD-like they can be as well in \i386\).

Maybe only NTDETECT.COM needs to be in root and SETUPLDR.BIN can be move to \i386\ but it makes anyway more sense to keep them "together".

 

:cheers:

Wonko



#49 bee4u

bee4u

    Frequent Member

  • Advanced user
  • 172 posts
  •  
    United Kingdom

Posted 14 October 2013 - 08:09 PM

@ Wonko the Sane  

Maybe only NTDETECT.COM needs to be in root and SETUPLDR.BIN can be move to \i386\ but it makes anyway more sense to keep them "together".

I put NTDETECT.COM  in root and SETUPLDR.BIN in \i386 folder  GUESS WHAT ....WORKING..TOOOOO.. :1st: :clap: :clapping: :thumbsup:

THANK YOU...SIR....LONG LIVE  Wonko the Sane. :clapping:



#50 cdob

cdob

    Gold Member

  • Expert
  • 1315 posts

Posted 14 October 2013 - 08:24 PM

I put NTDETECT.COM  in root and SETUPLDR.BIN in \i386 folder  GUESS WHAT ....WORKING..TOOOOO..


Do you like the current approach?

In addition:
One fixed name \winnt.sif is not flexible at a multi boot USB drive.

Yes, there are fixed strings inside setupldr.bin, e.g. \ntdetect.com at a hard disk device.
Strings can be changed and files renamed and relocated.

What about files

\XPRAM\w.f
\XPRAM\ND.COM
\XPRAM\SETUPLDR.BIN
\XPRAM\XP_RAM.img

\ntdetect.com --> \XPRAM\nd.com
\winnt.sif --> \XPRAM\w.f (rdpath adusgted to \XPRAM\XP_RAM.img)

That way, all LiveXP files are within one folder.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users