Jump to content











Photo
- - - - -

best commad line option to install g4d to PBR scripting


  • Please log in to reply
3 replies to this topic

#1 Technotika

Technotika

    Frequent Member

  • Advanced user
  • 419 posts
  • Location:United Kingdom
  •  
    United Kingdom

Posted 22 March 2011 - 11:12 AM


c:\Temp   <<<<contains gruninst, RMPARTUSB.exe, touchdrv.exe

ECHO LOADING GRUB4DOS TO PBR

grubinst (hd1,0)

ECHO FIX UP USING TOUCHDRV

touchdrv %LETTER%:

ECHO "DRIVE NOW BOOTABLE (PBR G4D)"

Hi Steve
I am just tweaking a rmprep script that you kindly helped me make a good few months back.

I am getting a lot of trouble with the above, simply that for some reason it doesn't seem to work.
The script runs fine with no errors but when come to test the usb it says invalid drive because
it wasnt made bootable.

I noticed there have been some updates to grubinst.exe in the latest edition of rmprep perhaps there is
a better way of running that command & do I still need touchdrv.

Many thanks (love F11 feature!:unsure:)

#2 Technotika

Technotika

    Frequent Member

  • Advanced user
  • 419 posts
  • Location:United Kingdom
  •  
    United Kingdom

Posted 22 March 2011 - 04:11 PM

think I worked this out

before the grubinst tool was run loads of stuff was copied to the USB - I managed to get it to work by running this BEFORE any copying went on - wierd but solved

#3 steve6375

steve6375

    Platinum Member

  • Developer
  • 7567 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 23 March 2011 - 10:38 AM

RMPartUSB makes it bootable (sets active flag on partition). Grub4dos should not change this.
If you omit the grub4dos command is it still bootable (but will fail to find the bootstrap file (ntldr or IO.SYS or bootmgr)?

#4 Technotika

Technotika

    Frequent Member

  • Advanced user
  • 419 posts
  • Location:United Kingdom
  •  
    United Kingdom

Posted 23 March 2011 - 12:54 PM

I think it had something to do with robocopy locking the drive - I read around and heard other people had this problem in a fashion. It's all working beautifully now - no need to worry thanks though.




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users