Posts made by Junkhacker

according to Tom’s release notes on r1263, the i believe new pxelinux.0 is a custom compiled ipxe kernel instead of an pxelinux kernel. i suspect there is a flaw in the embedded ipxe config file.

in your fog configuration page, there are settings for the locations for the locations of
FOG_TFTP_PXE_KERNEL, which is currently fog/kernel/bzImage it needs to just be bzImage
FOG_MEMTEST_KERNEL, which needs to just be memtest
and FOG_PXE_BOOT_IMAGE, which needs to just be init.gz

no editing of php files, all from the web interface

[quote=“ArchFan, post: 23627, member: 19266”] … the 2 required files[/quote]

2?

@BigMan99211 post a copy (remove your IP addresses if you care to) of the results you get from this url
(your-fog-server-address)/fog/service/ipxe/boot.php?mac=00:00:00:00:00:00

if you are interested in this stuff, you really need to look at the development going on in fog 0.33b.

Ubuntu 12.04

iPXE doesn’t resolve the UEFI situation, but it is a step toward a solution.

is the FOG PXE Boot menu configuration page working yet? and if so, do advanced configuration options now need to be in ipxe format instead of the old pxelinux format?

you can replace the drives with a larger size, just not a smaller size the the original computer the image was pulled from. the partition sizes will match the original.

partcat: my steps are if you wish to use single disk resizable, if you do not use a resizable option you do not need to take those extra steps

reefcrazed: if you installed by svn you navigate to the folder you downloaded it to and run “svn version”

partcat: if you replace the system’s BCD file before you pull the image (use the copy attached to my earlier post), the system will boot. assuming you have all the drivers and it’s a relatively normal install. the BCD file is located on the hidden first partition that’s about 100 mb. you’ll most likely need to use a live boot disk to do the file replacement.
replace the file, then pull the image. do not let the computer boot into windows between those two steps.

yep, thats almost certainly the BCD

desktop. you said it “messed up the OS” what exactly did it do. were you getting BSOD screens on reboot? 0xc00000f or 0xc00000e specifically?

just for a test, i pulled an Optiplex 9020 off the shelf, pulled an image off of it (multipart single - not resizeable ), and imaged it back to the machine. worked fine.

the windows 7 default setup creates a 100mb or so system recovery drive that’s hidden when actually booted into windows. it’s in this first partition of the drive in the directory “boot” directory. the file itself is a pain to edit, but just replacing it with the one I attached works, it is the one generated when you sysprep a machine, before you reboot and it reconfigures. if you are unfamiliar with editing BCD files and want to look inside it, i recommend the program BOOTICE.

not sure on reefcrazed’s issue, but if partcat is having bsod after using “single disk resizable” image, it’s because resizing the disk messes up with the data the BCD file uses to find the boot info. to create a “master” image using “single disk resizeable” you have to replace the BCD of with a generalized version, which windows will rebuild on reboot just if you syspreped. if you replace the BCD file with this file, your computer should boot.

[url=“/_imported_xf_attachments/0/542_BCD.zip?:”]BCD.zip[/url]

i may have messed up the formatting of the ipxe boot menu when i sent it to you last. here’s what should be in the php file.
note: the first line ipxe sees must be #!ipxe

[url=“/_imported_xf_attachments/0/540_boot.php.txt?:”]boot.php.txt[/url]

let me know if my instructions are not clear enough, or i’m missing something.

akismet, the spam blocker software