Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Loading spec packet failed, trying to wing it

164 views
Skip to first unread message

jason.h...@rcmp-grc.gc.ca

unread,
Jan 15, 2004, 11:57:27 AM1/15/04
to
Good Morning All,
I am having issues trying to boot the new Toshibas into the zen imaging
engine. If you use floppies as you may or may not know it craps out with a
kernel panic error right after it asks for the second disk. This is due to
the USB floppy as far as I have learned. OK so on to the cd boot which is
the recommended work around for such a problem. When trying to boot from
cd , be it modified or newest bootcd.iso from latest patch, it craps out
with the following error "ISOLINIX 1.62 2001-04-24 isolinux: Loading spec
packet failed, trying to wing it" It then says "found something at " It
proceeds to go through what it thinks are devices till finally it
states "isolinux: Failed to access CD-Rom device; boot failed "
The first line of the error message refers to spec packet the "spec"
packet is information from the CD-ROM that tells the system what make it
is, what speed, etc. The fact that the loader can't grok that indicates
that the BIOS does something weird with it. Solutions for this issue are
to boot from floppy, Vicious circle, or use PXE which we do not use. If
that is my only option I will use it. I have already spent a day on this
without any good results.
If you have any thoughts or solutions it would be a great help as I am
about to pull my hair out.

jason.h...@rcmp-grc.gc.ca

unread,
Jan 20, 2004, 2:58:26 PM1/20/04
to
In case anyone is interested. I have solved the issue by updating the
version on ISOLINUX novell uses in there bootcd.iso. I used the version
contained in syslinux-2.08 . Why is Novell using such an outdated version?
Any questions contact me by e-mail

Marcus Breiden

unread,
Jan 21, 2004, 5:08:56 AM1/21/04
to
In novell.support.management.zenworks.desktops.imaging,
says...

> In case anyone is interested. I have solved the issue by updating the
> version on ISOLINUX novell uses in there bootcd.iso. I used the version
> contained in syslinux-2.08 . Why is Novell using such an outdated version?
> Any questions contact me by e-mail
>

no idea, but did you thought about a coolsolution article?
--

If you are searching for drivers or have already compiled one take
a look at http://forge.novell.com/modules/xfmod/project/?zfdimgdrv

Marcus Breiden

Please change -- to - to mail me.
The content of this mail is my private and personal opinion.
http://www.edu-magic.net

jai...@accesscomm.ca

unread,
Jan 25, 2004, 6:51:41 AM1/25/04
to
Thanks. I submitted one on thursday :)

Marcus Breiden

unread,
Jan 25, 2004, 5:10:47 PM1/25/04
to
On Sun, 25 Jan 2004 11:51:41 GMT, jai...@accesscomm.ca wrote:

> Thanks. I submitted one on thursday :)

good... :-)

jason.h...@rcmp-grc.gc.ca

unread,
Feb 2, 2004, 3:40:01 PM2/2/04
to
Here is a little more detail on the solution for people that are asking.
You will have to know how to modify the bootcd.iso. You can use TID
10071344 for reference

After research to discover the workings of the Zenimaging boot process and
the use of ISOLINUX as the boot loader I followed logical trouble
shooting. I used the Redhat 9.0 ISO image to make bootable CDs. The Redhat
9 install cd also uses isolinux as a bootloader. With this cd I am able to
boot up the Toshiba Tecra S1, identify the cd-rom drive and proceed with
install. Using this info I downloaded the latest version of SYSLINUX 2.08
(http://syslinux.zytor.com/ that is the homepage but at time of writing
this it was down...oh well it's download section links to this url anyway
http://www.kernel.org/pub/linux/utils/boot/syslinux grab whichever package
type you prefer) and used the version of ISOLINUX contained in this
version. I replaced the ISOLINUX.BIN (version 1.62) file inside the
bootcd.iso supplied by Novell dated 2001-04-24 with the newest
ISOLINUX.BIN dated 2003-12-12 (version 2.08). With the newest isolinux in
place I repackaged the bootcd.iso, booted the laptop in question, all
devices were identified and we were back in the imaging business. Seems
like a simple procedure when written down. Also if you are using linux I
would recommend finding the syslinux folder on your box and updating the
files inside to the newest versions also.

Marcus Breiden

unread,
Feb 2, 2004, 6:00:17 PM2/2/04
to
On Mon, 02 Feb 2004 20:40:01 GMT, jason.h...@rcmp-grc.gc.ca wrote:

> Here is a little more detail on the solution for people that are asking.

Thanks Jason..

hope to see the coolsolution article soon..

0 new messages