Jump to content











Photo
- - - - -

Boot BOOTSDI.IMG as drive C: ?


  • Please log in to reply
5 replies to this topic

#1 gbrao

gbrao

    Frequent Member

  • Advanced user
  • 370 posts
  •  
    India

Posted 12 September 2012 - 12:01 PM

When BOOTSDI.IMG is booted from g4d, the 'boot drive/s' end up as X: & B:.

Is it possible to modify/replace files in the IMG so that it boots as C: ? Like a 'regular' XP ?

What is the exact boot sequence for a BOOTSDI.IMG ?

#2 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 12 September 2012 - 01:49 PM

See if this helps (about the X: ):
http://reboot.pro/15199/
http://reboot.pro/1938/

The B: should be the (additional) Ramdisk. :unsure:

The common mistake people commits when dealing with the LiveXP BootSDI is thinking that in the booting an actual SDI is involved :w00t:.
(but that's allright, since also LiveXP is NOT a "Live XP" but a PE 1.x ;))
The LiveXP BootSDI is a "normal", "plain", Ramdisk booting of a RAW image, see:
http://reboot.pro/15...__50#entry10860
http://reboot.pro/in...?showtopic=6344
AND links within.

:cheers:
Wonko

#3 gbrao

gbrao

    Frequent Member

  • Advanced user
  • 370 posts
  •  
    India

Posted 12 September 2012 - 08:03 PM

I managed to boot BOOTSDI as C:.

https://sites.google...images/sdi1.png

I booted BOOTSDI using g4d and got the values :

[HKEY_LOCAL_MACHINESYSTEMMountedDevices]

"??Volume{32b27be2-fd3b-11e1-bdd2-806d6172696f}"=hex:80,00,00,00,00,7e,00,

00,00,00,00,00

"DosDevicesX:"=hex:80,00,00,00,00,7e,00,00,00,00,00,00


Rebooted to HDD XP.
Mounted BOOTSDI.IMG with imdisk, used 'reg load' on setupreg.hiv,
https://sites.google...images/sdi2.png

Added the 'MountedDevices' as
https://sites.google...images/sdi3.png
note the C:

did a 'reg unload'

unmounted BOOTSDI.IMG.

booted BOOTSDI.IMG with g4d (from RAM).

Edit : "set" : https://sites.google...images/sdi4.png

#4 gbrao

gbrao

    Frequent Member

  • Advanced user
  • 370 posts
  •  
    India

Posted 13 September 2012 - 03:59 AM

After modifying this :
https://sites.google...images/sdi5.png

"set" shows :
https://sites.google...images/sdi7.png

when are APPDATA, HOMEDRIVE & TEMP set ?

when is ModelRam.exe unzipped to B ? Edit : by runonce.

#5 joakim

joakim

    Silver Member

  • Team Reboot
  • 912 posts
  • Location:Bergen
  •  
    Norway

Posted 13 September 2012 - 06:04 AM

There's likely quite a few paths you would need to change in the registry when tweaking the mountpoint like that. I once made a program for this when testing this sort of sort, but can't find it. It was basically just search & replace for registry. On the other hand, it could be that your build is based on well written written scripts that use very little hardcoded paths.

#6 gbrao

gbrao

    Frequent Member

  • Advanced user
  • 370 posts
  •  
    India

Posted 13 September 2012 - 06:12 AM

right now there are no user scripts. i just was wondering if i could make a livexp img that boots to only C:. and maybe end up with a 'universal-live xp' on a img - one that i can directly install stuff to or modify (when booted as filedisk). maybe i'm hoping for too much.

edit : managed to get everything on C:, installed a few programs ok, installed intel chipset driver ok, installed pathcopy from a .inf file, but ... all when booting from RAM.
the .img won't boot as filedisk, error 6b. maybe i should have used winvblk instead of firadisk as per wimb's universal xp. anyway ...




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users