Include DOS based applications into the PXE boot menu
I recently have set up a FOG machine, I have successfully added items to the PXE menu. I have added a few .iso files and they are all working brilliantly.
However I was wondering if it is possible to add a ghost .vfd file to the menu. I have tried just adding the .vfd file, this didn’t work. I also created a .iso from the files within the .vfd but still no luck.
The fog wiki has a webpage for this but when you click the link it is a dead link. I was wondering if anyone out there has achieved this and would be willing to share their wisdom please.
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.
If you would like me to, I think I still have a undi universal boot CD ISO for ghost that I could send. I think its all scripted, but you could extract the auto execs and edit them as necessary.
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.
I’m assuming the 2nd error happens on the client youre using to test PXE booting, which might make sense. I would probably venture a guess that the Client being virutalized is the reason for that error. You’re essentially switching to a DOS/Floppy based environment and the virtual machine may be getting confused. That’s only my guess though and not very educated either as I never really worked in a dual virutalized environment (our FOG servers are bare metal and I would occasionally use a virtual machine to test PXE menu stuff).
I would recommend trying to boot to your fog server from a bare metal client and seeing how it reacts if you have the luxury.
Just curious, from the menu options, are you trying to make a UNDI symantec ghost client to boot in fog?
Both are virtualized, I’m testing it before I let it loose live on the domain.
[quote=“Rob Wood, post: 3208, member: 1025”]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?
Let me make sure I’m clear on this, is your FOG server virtualized? Or is the client you’re using to test the PXE booting virtualized?
*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?
Change the “iso” after append to “floppy”, that might fix it.
The .vfd is 2.81mb
Here is the code I am using.
LABEL Ghost HP client
MENU MASTER PASSWD password
append iso initrd=fog/ghost/hp/hp.vfd raw
MENU Label Ghost client with HP nic
Ghost client with NIC drivers for HP
[quote=“Rob Wood, post: 3191, member: 1025”]
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.[/quote]
Well, maybe. How big is the VFD? It maybe a memory issue. Memdisk dumps the whole image to RAM so if you don’t have enough RAM, the system will fail out.
Could you possibly share your pxelinux.0 entry for this boot option? We may need to change some appends.
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.
What kernel are you using to boot the vfd files? memdisk?