Jump to content











Photo
- - - - -

Live xp and BootSDI


  • Please log in to reply
62 replies to this topic

#1 bee4u

bee4u

    Frequent Member

  • Advanced user
  • 172 posts
  •  
    United Kingdom

Posted 10 October 2013 - 02:14 AM

i made live xp with BootSDI option , the iso works perfectly in VM even on usb with grub4dos commands.e.g

title LiveXP_RAM
find --set-root --ignore-floppies/LiveXP_RAM.iso
map /LiveXP_RAM.iso (hd32)
map --hook
chainloader (hd32)

But when i boot it on real pc cd works ok not the usb , if i add --mem command then it  works ok on usb too.

why it needs --mem command for usb on real pc and not in VM..?

 

How to boot BOOTSDI.IMG of live xp on usb...? i get error file not found  (hd0,0)/NTLDR  with following commands:

title LiveXP-BootSDI
map /I386/BOOTSDI.IMG (hd0)
map --hook
chainloader (hd0,0)/NTLDR

Waiting for solution THX in advance.... :smiling9:

 

 



#2 bee4u

bee4u

    Frequent Member

  • Advanced user
  • 172 posts
  •  
    United Kingdom

Posted 10 October 2013 - 02:40 PM

any one point to the solution ...waiting ...thx



#3 bee4u

bee4u

    Frequent Member

  • Advanced user
  • 172 posts
  •  
    United Kingdom

Posted 10 October 2013 - 04:02 PM

@ Wonko the Sane kindly give your expertise solution for my query..?....... :dubbio:



#4 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 10 October 2013 - 06:15 PM

@ Wonko the Sane kindly give your expertise solution for my query..?....... :dubbio:

I guess you need more Amalux's than my assistance.

 

However:

http://reboot.pro/to...ivexp-from-usb/

http://reboot.pro/to...-portable-apps/

 

All I can do is pointing you back to Amalux's tutorials and "surely working" builds:

http://reboot.pro/to...img-for-livexp/

 

The original posting, available here as .pdf is possibly clearer (as it doesn't mix in the middle the 7PE build):

http://amalux.winbui...XP with BootSDI!.pdf

 

 

:cheers:

Wonko



#5 bee4u

bee4u

    Frequent Member

  • Advanced user
  • 172 posts
  •  
    United Kingdom

Posted 11 October 2013 - 12:45 AM

 

How to boot BOOTSDI.IMG of live xp on usb...? i get error file not found  (hd0,0)/NTLDR  with following commands:

title LiveXP-BootSDI
map /I386/BOOTSDI.IMG (hd0)
map --hook
chainloader (hd0,0)/NTLDR

Waiting for solution THX in advance

i mean the grub4dos commands to run BOOTSDI.IMG of live xp from usb. cuz i get error file not found  (hd0,0)/NTLDR

BOOTSDI.IMG on  cd works ok...only this issue remains...THX



#6 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 11 October 2013 - 04:57 PM

Well, that may be due to a number of reasons.

If I recall correctly, the image is "wrongly" called SDI, since it is not a SDI image at all, but a plain, RAW image.

 

Cannot remember if it is a "full disk" image or a "volume image". :unsure:

 

The usual rule of the thumb, when experimenting is to NEVER use a pre-made menu.lst BUT use Command Line instead.

 

Just issue at the grub> prompt the lines one by one and report if there is any feedback.

 

If you can get to the point BEFORE the "chainloader" command without any error/warning, try issuing the following commands:

cat --hex --length=16 --skip=0 (hd0)0+1

and

cat --hex --length=4 --skip=440 (hd0)0+1

and

cat --hex --length=16 --skip=446 (hd0)0+1

and

cat --hex --length=2 --skip=510 (hd0)0+1

 

the first one will print on screen first 16 bytes of the first sector of the mapped disk (enough to verify it is a MBR code).

the second one will print on screen the Disk SIgnature.

the third one will print on screen the first entry in the partition table (i.e. the addresses/partition ID of the (hd0,0) partition).

the fourth one will print on screen the "Magic Bytes".

 

The above if the image is a "whole disk" image.

If it is a "volume" or "superfloppy" image, it's first sector will be a bootsector instead, here are the "common" first few bytes of bootsectors and MBR's:

http://reboot.pro/to...ge-file-offset/

http://reboot.pro/to...offset/?p=14502

 

Report what happens.

 

:cheers:

Wonko



#7 bee4u

bee4u

    Frequent Member

  • Advanced user
  • 172 posts
  •  
    United Kingdom

Posted 12 October 2013 - 03:42 AM

when run from menu.lst  it shows

probed C/H/S = 11/255/63, probed total sectors = 176715
chainloader (hdo,0)/NTLDR
error 15: file not found

 

when run in  grub> map /I386/BOOTSDI.IMG (hd0)   it shows only error 15 file not found

i cannot  get to the point BEFORE the "chainloader" command without any error/warning

 

one thing more i noticed if i run this BOOTSDI.IMG first through menu.lst it shows error as above error 15: file not found then i go back to menu and select other iso to run it gives same error 15: file not found although this  iso runs well before and when i reboot and come back to grub4dos menu and select same iso it runs ok i am using grub4dos  0.4.5c 2013-07-24    :confused1:



#8 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 12 October 2013 - 10:34 AM

No.

You are doing something wrong .

 

at the grub> prompt type just:

map /

and press the [TAB] key, this will list the files in the current root directory.

If you cannot find the /I386/ directory it means that you are root on the "wrong" device.

 

BTW your commands are "vague".

On command line, try:

find --set-root /i386/bootsdi.img
map /i386/bootsdi.img (hd0)
map --hook

and then run the set of cat --hex commands.

 

:cheers:

Wonko



#9 bee4u

bee4u

    Frequent Member

  • Advanced user
  • 172 posts
  •  
    United Kingdom

Posted 12 October 2013 - 09:28 PM

At the grub> map / and press the [TAB] key  showed the content of drive and  /I386/ directory is shown too and at commandline entered:

find --set-root /i386/bootsdi.img
map
/i386/bootsdi.img (hd0)
map --hook

 

find --set-root /i386/bootsdi.img    showed  (hd0,0)

map /i386/bootsdi.img (hd0)     showed  probed C/H/S = 11/255/63, probed total sectors = 176715

map --hook     showed    grub> 

no errors are shown  BEFORE the "chainloader" command  and following commands are used which showed different hex codes

cat --hex --length=16 --skip=0 (hd0)0+1

and

cat --hex --length=4 --skip=440 (hd0)0+1

and

cat --hex --length=16 --skip=446 (hd0)0+1

and

cat --hex --length=2 --skip=510 (hd0)0+1

 

the i386 directory contains  bootsdi.img , bootsdi.pln , ntdetect.com , projectinfo.ini , setupldr.bin    on the usb



#10 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 13 October 2013 - 09:35 AM

Sometimes I wonder if there is something wrong in the way I express myself.

 

 

Report what happens.

 

Of course you get "different hex codes" when accessing different locations.

Now what would be sensible would be to either know WHAT those "different hex codes" mean OR post them, so that someone who knows what they are can check them.

"Report" in this case (in my perverted mind) means "produce the acatual results of the three cat --hex command by either typing them or posting three images of the result", and not report "if you get some different hex codes".

 

I will try again.

By using the commands:

 

find --set-root /i386/bootsdi.img showed (hd0,0)

map /i386/bootsdi.img (hd0) showed probed C/H/S = 11/255/63, probed total sectors = 176715

map --hook showed grub>

 

you undoubtedly mapped the bootsdi.img as (hd0), now it is time to verify that bootsdi.img is actually a valid "full" hard disk image, i.e. if it's first sector is actually a MBR or not.

This is the scope of inspecting the first sector using the cat --hex command.

 

:cheers:

Wonko



#11 cdob

cdob

    Gold Member

  • Expert
  • 1314 posts

Posted 13 October 2013 - 02:22 PM

But when i boot it on real pc cd works ok not the usb , if i add --mem command then it works ok on usb too.

why it needs --mem command for usb on real pc and not in VM..?

How do you use the USB drive at VM?
Do you map the USB drive to a virtual internal hard disk?
 

How to boot BOOTSDI.IMG of live xp

Dosn't use LiveXP file bootsdi.wim?

How do you create bootsdi.img?
Which layout do you use? Which files are inside the image?

#12 bee4u

bee4u

    Frequent Member

  • Advanced user
  • 172 posts
  •  
    United Kingdom

Posted 13 October 2013 - 03:24 PM

@ Wonko the Sane sorry pal didnt report back fully... :blush:  i have attached result of cat commands

 

@ cdob

 

How do you use the USB drive at VM?

for VM  i use  Mobalivecd run the live usb option and  Qemu Simple Boot v1.2  bootable media  hdd, on the real pc from usb with grub4dos

 

Do you map the USB drive to a virtual internal hard disk?

i dont understand...?

 

Dosn't use LiveXP file bootsdi.wim?  How do you create bootsdi.img?
Which layout do you use? Which files are inside the image?

no i used only bootsdi script no wim ,  i created bootsdi.img form using bootsdi script with suppling ramdisk and w2k3sp1 files iso then copying i386 directory from ram directory created by bootsdi script on to usb,  the files inside image are  i386 directory  program files  bootflag  modelram.exe

Attached Thumbnails

  • cat.jpg


#13 cdob

cdob

    Gold Member

  • Expert
  • 1314 posts

Posted 13 October 2013 - 04:15 PM

Mobalivecd

This does NOT boot from USB.
The USB disk is mapped to a hard disk.
The virtual machine boots from this virtual hard disk. This is not USB booting.
 

bootsdi script

I'm not familiar with this one.
 

suppling ramdisk and w2k3sp1 files iso

The 2003 ramdisk driver dosn't support a grub4dos disk.
Booting with a grub4dos disk will fail.

#14 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 13 October 2013 - 04:29 PM

The 2003 ramdisk driver dosn't support a grub4dos disk.
Booting with a grub4dos disk will fail.

Well, this may depend. :dubbio:

I suspect that the method is similar to this one:

http://reboot.pro/to...ge-2#entry42525

 

@bee4u

The image is that of a "full" hard disk.

Now issue on command line:

find --set-root /i386/bootsdi.img
map /i386/bootsdi.img (hd0)
map --hook
root (hd0,0)
chainloader /

and press the [TAB] key.

Do you see NTLDR (or SETUPLDR.BIN) listed?

Do you see a WINNT.SIF listed?

 

IF not try with:

chainloader /i386/

[TAB]

 

Post contents of WINNT.SIF (afaik it must be in ROOT, not in \i386\)

 

:cheers:

Wonko



#15 bee4u

bee4u

    Frequent Member

  • Advanced user
  • 172 posts
  •  
    United Kingdom

Posted 13 October 2013 - 05:06 PM

@ Wonko the Sane with root (hd0,0)  shows error 17: cannot mount selected partition

chainloader press the [TAB] key  not showing  NTLDR (or SETUPLDR.BIN) WINNT.SIF

chainloader /i386/  press the [TAB] key  not showing  NTLDR (or SETUPLDR.BIN) WINNT.SIF but showing some other files like explorer.exe fonts  textsetup.sif winsxs etc

 

@cdob

 

The 2003 ramdisk driver dosn't support a grub4dos disk.
Booting with a grub4dos disk will fail.

    But it boots the iso made by2003 sp1 files with bootsdi with grub4dos map --mem commands on real pc with usb                            



#16 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 13 October 2013 - 05:35 PM

No. :(

The results of the cat --hex that you posted tell me that the image is a whole disk image (i.e. that it's first sector is a MBR).
There is a first partition, it is active, it is NTFS, starts at LBA sector 63, it is 176652 sectors in size (and 63+176652=176715, detected by the mapping)
There is no apparent reason why you cannot root to it. (and there is NO SENSE whatsoever in issuing commands related to a partition if you cannot access it).
That error would happen if the volume in the partition is not formatted or misses a valid bootsector. :w00t:
 
Are you really sure-sure that you typed the commands correctly?
Just for the experiment, can you try running these commands:
 
 
 
find --set-root /i386/bootsdi.img
map /i386/bootsdi.img (hd31)
map --hook
geomeetry (hd31)
root (hd31,0)
:cheers:
Wonko

#17 bee4u

bee4u

    Frequent Member

  • Advanced user
  • 172 posts
  •  
    United Kingdom

Posted 13 October 2013 - 06:52 PM

@ Wonko the Sane     yes may be some typo error now  root (hd0,0)  shows filesystemtype is ntfs  but not showing  NTLDR (or SETUPLDR.BIN) WINNT.SIF

i have attached the pic result of post 14  and post 16

BTW my 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 .

Attached Thumbnails

  • root.jpg
  • 31.jpg


#18 cdob

cdob

    Gold Member

  • Expert
  • 1314 posts

Posted 13 October 2013 - 07:19 PM

But it boots the iso made by2003 sp1 files with bootsdi with grub4dos map --mem commands on real pc with usb

Either there is another ramdisk driver too. Do you add firadisk or winvblk?
Or there is adouble ram loading, setupldr.bin loads the image to RAM too and 2003 ramdisk access this.

Which files and folders are inside LiveXP_RAM.iso?
List all files.

#19 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 13 October 2013 - 07:32 PM

Ok, but somewhere a WINNT.SIF is needed.

Make a file called WINNT.SIF ( a simple text file, you can use NOTEPAD) in the root of the stick, with these contents:

[SetupData]

BootDevice = "ramdisk(0)"

OsLoadOptions = "/noguiboot /fastdetect /rdexportashd /rdimageoffset=32256 /rdpath=BOOTSDI.IMG"

 

 

Then boot to grub4dos, on command line:

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

What happens?

 

:cheers:

Wonko



#20 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 13 October 2013 - 08:12 PM

@cdob
bootsdi.img was the precessor of bootsdi.wim

@all
Boot order
- g4d
- ntldr (renamed setupldr)
- ntldr reads winnt.sif
- ntldr loads bootsdi.img into ram
- ntldr mounts the image
- ntldr reads txtsetup.sif from the image
- ntldr starts loading the OS from the image

Therefore, g4d does not need to map anything / load anything. Just chainload ntldr(which is outside of bootsdi.img!).

:cheers:

#21 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 13 October 2013 - 08:22 PM

@bee4u
Can you post a directory listing of your USB-Drive?

:cheers:

#22 cdob

cdob

    Gold Member

  • Expert
  • 1314 posts

Posted 13 October 2013 - 09:32 PM

bootsdi.img was the precessor of bootsdi.wim

Thank for the reminder, I remember the 2003 ramdisk basics, eight years ago http://www.911cd.net...showtopic=10482

 

title LiveXP_RAM
find --set-root --ignore-floppies/LiveXP_RAM.iso
map /LiveXP_RAM.iso (hd32)
map --hook
chainloader (hd32)
But when i boot it on real pc cd works ok not the usb , if i add --mem command then it  works ok on usb too.
why it needs --mem command for usb on real pc and not in VM..?

What happens without --mem at a real pc?
Any error mesage? Which one?

#23 bee4u

bee4u

    Frequent Member

  • Advanced user
  • 172 posts
  •  
    United Kingdom

Posted 14 October 2013 - 02:53 AM

@cdob

 

Either there is another ramdisk driver too. Do you add firadisk or winvblk?
Or there is adouble ram loading, setupldr.bin loads the image to RAM too and 2003 ramdisk access this.
Which files and folders are inside LiveXP_RAM.iso?
List all files.

What happens without --mem at a real pc?
Any error mesage? Which one?

No other ramdisk driver only  2003 ramdisk files  , no duble ram loading, LiveXP_RAM.iso folder i386 ,  files pe.drive ,winntsif in the root  and in

I386 directory (BOOTSDI.IMG , BOOTSDI.PLN, NTDETECT.COM , SETUPLDR.BIN , PROJECTINFO.INI  ) filles.

at  real pc without mem on desktop dual core  pc it reboots to grub menu  but with mem it loads, on  laptop core i3 it boots without mem

 

@ Wonko the Sane   it gives error 15 file not found , pic attached.

 

@ MedEvil

 

Can you post a directory listing of your USB-Drive?

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

Attached Thumbnails

  • wn.jpg


#24 cdob

cdob

    Gold Member

  • Expert
  • 1314 posts

Posted 14 October 2013 - 04:25 AM

no duble ram loading

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

LiveXP_RAM.iso folder i386 ,  files pe.drive ,winntsif in the root

There it is, post the winnt.sif.
 

at  real pc without mem on desktop dual core  pc it reboots to grub menu  but with mem it loads, on  laptop core i3 it boots without mem

It works at some real pc, but not all.
That's a BIOS case.
 
Which hardware do you use?
Which desktop and whitch laptop?

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


#25 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 14 October 2013 - 08:39 AM

@ Wonko the Sane   it gives error 15 file not found , pic attached.

My bad, I forgot that you have the image in the /I386/ directory.

Try:

 

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

 

 

CHECK what you type, in any case "/[SPACE]/setupldr.bin" is NOT the same as "/setupldr.bin".

 

The booting sequence is the one Medevil suggested :thumbsup:, re-post the list of files. (of course invoking a real SETUPLDR.BIN, or a SETUPLDR.BIN renamed to NTLDR is the same thing).

A WINNT.SIF is NEEDED, and on a hard disk like device it needs to be in root, if I recall correctly, but if you place for experiment two copies, one in root and on in the /i386/ directory it won' t be a problem. 

 

 

:cheers:

Wonko






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users