Jump to content











Photo
- - - - -

using tut#43 and want to a syslinux bootcd


  • Please log in to reply
7 replies to this topic

#1 swindmiller

swindmiller

    Newbie

  • Members
  • 15 posts
  •  
    United States

Posted 19 March 2013 - 01:24 AM

I am using tutorial 43 and have several iso's booting fine with it but am having trouble booting a Novell Zenworks imaging boot cd. I am able to get it to boot by extracting the contents from the iso and using syslinux to boot it using this:

 

Label manual
  MENU LABEL Manual Mode
  kernel /ubnkern
  append initrd=/ubninit ramdisk_size=67584 vga=0x0314 splash=silent mode=5 USBBOOT=YES showopts install=hd:/dev/sdb1 root=/dev/sdb1

I want to be able to boot the actual iso which would make updating the iso so much easier but I am not sure how to integrate it with what I already have.

 

Thanks,

Scott



#2 steve6375

steve6375

    Platinum Member

  • Developer
  • 7188 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 19 March 2013 - 11:16 AM

Try the partnew method - note you MUST have the 4th partition table entry free  (use RMPrepUSB - Drive Info - 0 to check if you are not sure!)

 

title Zenworks
map /zenworks.iso (0xff)
map --hook
partnew (hd0,3) 0x0 /zenworks.iso
rootnoverify (0xff)
chainloader (0xff)

Or better yet, try Easy2Boot v1  !!!



#3 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 19 March 2013 - 11:22 AM

Still in an attempt to avoid (rare but possible) issues, you can also verify that the partition entry ID is 0x00 before writing to it directly in the grub4dos entry:

http://reboot.pro/to...rided/?p=164127

 

:cheers:

Wonko



#4 swindmiller

swindmiller

    Newbie

  • Members
  • 15 posts
  •  
    United States

Posted 19 March 2013 - 02:27 PM

Thanks for the reply!!

 

This does make the ISO boot but during the boot there is a Settings.txt file that is read and it looks like it stops booting at that point. Is it possible the ISO is not mounted right so it cannot be read? Sorry but I am really new to this and trying to learn as I go along :)

 

I ran the Disk Info from RMPrepUSB and this is what I got...not really sure what I am looking at:

 

 

Disk Signature bytes (1B8h-1BBh) = A1 F6 9E 20

Partition 1   SIZE=61079.969MiB   Type: 0C FAT32LBA (2047GB max)  *ACTIVE*
START POS   = CYL:0 HD:1 SEC:1  END POS = CYL:1023 HD:254 SEC:63
START (LBA) = 63 (0000003F)      SIZE (LBA) = 125,091,777 (0774BFC1)

Partition 2   SIZE=0.031MiB   Type: 21 Hidden(rsvd)       
START POS   = CYL:1023 HD:254 SEC:63  END POS = CYL:1023 HD:254 SEC:63
START (LBA) = 125,091,840 (0774C000)      SIZE (LBA) = 63 (0000003F)

Partition 3   SIZE=0MiB   Type: 00        
START POS   = CYL:0 HD:0 SEC:0  END POS = CYL:0 HD:0 SEC:0
START (LBA) = 0 (00000000)      SIZE (LBA) = 0 (00000000)

Partition 4   SIZE=88.15MiB   Type: 00        
START POS   = CYL:1023 HD:191 SEC:39  END POS = CYL:1023 HD:252 SEC:12
START (LBA) = 112,916,891 (06BAF99B)      SIZE (LBA) = 180,532 (0002C134)

P1   Start=63 (32,256 bytes) End=125,091,839 (64,047,021,568 bytes)
P2   Start=125,091,840 (64,047,022,080 bytes) End=125,091,902 (64,047,053,824 bytes)


Drive 3 Corsair Survivor 3.0 is 64,047,022,080 bytes long (59.648GiB)
F/W Rev.=1.00  Serial No.= [ 00 00 00 00 00 00 00 00 ]

Thanks for the help!!


Edited by swindmiller, 19 March 2013 - 02:28 PM.


#5 steve6375

steve6375

    Platinum Member

  • Developer
  • 7188 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 19 March 2013 - 03:18 PM

You mean it starts to boot from the ISO?

If so then it looks like partnew will not work.



#6 swindmiller

swindmiller

    Newbie

  • Members
  • 15 posts
  •  
    United States

Posted 19 March 2013 - 03:45 PM

You mean it starts to boot from the ISO?

If so then it looks like partnew will not work.

Yes it starts to boot and then stops when it needs to read the .txt file. Is there anything else I can try?



#7 steve6375

steve6375

    Platinum Member

  • Developer
  • 7188 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 19 March 2013 - 03:54 PM


 

title test 1 - extract files from ISO
kernel /ubnkern ramdisk_size=67584 vga=0x0314 splash=silent mode=5 USBBOOT=YES showopts install=hd:/dev/sdb1 root=/dev/sdb1
initrd /ubninit 


title test 2 - using ISO - make sure no extracted files are on USB drive
map /zenworks.iso (0xff)
map --hook
root (0xff)
kernel /ubnkern ramdisk_size=67584 vga=0x0314 splash=silent mode=5 USBBOOT=YES showopts install=hd:/dev/sdb1 root=/dev/sdb1
initrd /ubninit 

 

 

 
you may also require a cheatcode in the kernel line - you can try looking in the init script to see if there is one and what form it takes. 


#8 steve6375

steve6375

    Platinum Member

  • Developer
  • 7188 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 19 March 2013 - 04:16 PM

From the website:

 

 

Linuxrc attempts to locate and load the settings.txt file, either on the root of the imaging CD, or on the ZENworks Imaging server in the TFTP directory. From settings.txt, linuxrc reads and processes any parameters that pertain to itself, then copies settings.txt to the root (/) of the file system.

Linuxrc then also attempts to locate and load a file named driverupdate. It is usually located in the same directory as root. This file is used to update drivers and other files in the imaging distribution.

The driverupdate file is based on standard SUSE technology during a PXE boot. Because the network must be operating normally in order to obtain driverupdate, this file cannot update drivers for the active network device. However, other files and drivers can be updated by using the driverupdate file. For more information, see Section F.4.3, Using the Driverupdate File Method.

 

 

So you may need to extract the settings.txt to the root of your USB drive too???






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users