Thank you for the replies,

Yes I am using it in a virtual environment at the moment before I let it live on the domain. I think I’m going to build a new one on a physical machine, as to change it from SCSI to IDE I would have to rebuild it virtually, so I might as well just build it properly so I can use it on the domain.

I’ll have to check out that article and see what’s occurring.

It just seems strange that I can boot other utilities from a .iso file but not a live CD. Hope fully what you guys have recommended works, I’ll let you know how it goes.

Thanks again for your input.

I haven’t updated it I’m afraid, I’m using fog_0.32 at the moment.

I have attached a screenshot of the error that I get when I try and boot the Ubuntu live CD. I get a similar error when I try the Linux mint live CD as well. Both complain about containing a live file system.

Also here is the syntax from my default file.

LABEL Ubuntu Live CD
MENU MASTER PASSWD password
kernel fog/ubuntu/memdisk
append iso initrd=fog/ubuntu/ubuntu.iso raw
MENU Label Ubuntu CD
TEXT HELP
Ubuntu Live CD for retriving files
ENDTEXT

Regards

Rob

[ATTACH=full]121[/ATTACH]

[url=“/_imported_xf_attachments/0/121_ubuntu live cd error.jpg?:”]ubuntu live cd error.jpg[/url]

Hi there,

A couple of months ago I set up a FOG server and with the help of you guys was able to boot ghost .vfd files as well as our utilities in .iso form.

I was wondering if I could ask of your help again please. I’m trying to boot a linux liveCD from the menu. It boots from the menu but as it is about to go into the desktop it gives a error. I am using the same syntax to boot from a normal .iso file. I can provide screenshots if required.

I would be most grateful if anyone could lend a hand please.

Reagrds

Rob Wood

I just created a .vfd file the same way I would make one with the NIC specific .dos file but using the UNDI .dos file and added it to our current Symantec PXE server. I have tested four different machines that I know use four different NIC drivers, all four booted into ghost and I was able to connect to a session. So it was as easy as what I hoped, I guess there could be some NIC’s it might not support but everything I have tested seems to work so far.

But thank you for your offer.

Regards

Rob

Aye I had a feeling at the back of my mind that it might be because it is a virtual machine when I saw that error. I will try and find an old physical machine and give it ago. I will let you know what I find.

At the moment I’m just trying to get one of our current .vfd files working. Since beginning this post I have been told about UNDI, so that will be my next project. Hopefully it will just be a case of taking out of the NIC specific .dos file and use the UNDI .dos file instead. But I’m sure it can’t be that easy.

Both are virtualized, I’m testing it before I let it loose live on the domain.

*but I got the following

I tried changing the iso to floppy. I should explain I’m testing this in a virtual environment. my virtual client booted but I go the following screen followed by the following error. I’m not sure if this would be different on a physical machine or not. Do you think it is just because it is a virtual machine?

[url]http://dl.dropbox.com/u/5714699/screen.jpg[/url]
[url]http://dl.dropbox.com/u/5714699/screen - error.jpg[/url]

Regards

Rob

The .vfd is 2.81mb

Here is the code I am using.

LABEL Ghost HP client
MENU MASTER PASSWD password
kernel fog/ghost/hp/memdisk
append iso initrd=fog/ghost/hp/hp.vfd raw
MENU Label Ghost client with HP nic
TEXT HELP
Ghost client with NIC drivers for HP
ENDTEXT

Yes I am using memdisk. Here is a link to a screenshot of what the error is [url]http://dl.dropbox.com/u/5714699/3.jpg[/url]

Since posting this someone informed me that dos can only use files that are 680kb or smaller, hence why it is complaining about it being too large.