Wolfbane, i know the wiki has pages for “working devices” and “problematic device” but i recommend that you flag those both as “legacy” and create a single new page for working and non-working devices, so it can be searched more easily

he is running 0.32, so it shouldn’t be a undionly.kpxe problem. i would say that i think this is more likely a “0.32 doesn’t like linux” issue, but the screenshots look like the image profile settings don’t match the actual image file data.

the tftpboot folder, yes

please update to the latest version of undionly.kpxe in the svn trunk. we believe we may have the issue finally fixed.
details: [url]http://fogproject.org/forum/threads/040ee119-error-on-boot.10493/page-3#post-28887[/url]

the tftp server only hosts the undionly.kpxe and default.ipxe
the undionly.kpxe is, more or less, the the base kernel of ipxe with a single instruction added to it: load default.ipxe
default.ipxe is created by the install script with a single basic purpose, load the boot.php file according to the settings on the server
the boot.php file is web based, and is the source of menus, including the background

please update to the latest version in the svn trunk. we believe we may have the issue finally fixed.
details: [url]http://fogproject.org/forum/threads/040ee119-error-on-boot.10493/page-3#post-28887[/url]

what version of fog are you running?
1.0.1 official release or an svn release?

DISKPART erases partitions, but i don’t think it modifies the boot sector. you didn’t wipe the old gpt data off the drive. you can use gdisk to wipe the boot sector

can you log into the webgui?

you’ll want to enable FOG_LEGACY_FLAG_IN_GUI IN the general settings section of fog settings, then change the value on the images

i have had a lot of success without using sysprep or fogprep.

last night, tom added a new feature to the development release of fog. if you install the svn version of fog, you will find a new option of “grub” for exit type. that will load the grub4dos boot-loader, which is known to exit cleanly on a wide variety of systems, and boot to hard disk.

i’m having a hard time understanding when and where a 4 minute wait time for a diagnostic disk to load is not viable for production

the undionly.kpxe file automatically searches for default.ipxe in the same directory as itself.
changing that setting requires recompiling undionly.kpxe

so far as i know, single disk resizable is only usable on ntfs partitions

those 2 places in config.php are no longer used
have you changed the password to match in Fog Settings -> TFTP Server -> FOG_TFTP_FTP_PASSWORD

a link to Jaymes’s wiki on dnsmasq [url]http://www.fogproject.org/wiki/index.php/Setting_up_ProxyDHCP[/url]

what type of DHCP server are you using?
can you retrieve the file with this command?
[FONT=Consolas]tftp -i <server IP> get default.ipxe[/FONT]

ok, the sandbox thing isn’t relevant for you then. are you certain that the linux user “fog” has it’s password set to the same as is listed in the fog settings?

I have created a wiki page for the Advanced boot menu stuff
[url]http://www.fogproject.org/wiki/index.php/Advanced_Boot_Menu_Configuration_options[/url]