@Junkhacker Done 🙂 https://github.com/FOGProject/fogproject/commit/f943e3a8690110fd7b469b40e38f3d26512ddc18

@Junkhacker further testing suggests that everything works fine without the --ignore_crc flag we have set in all restore operations. i’ve also learned that due to a bug in partclone 2.89, the checksums it was making were practically useless. if/when we upgrade to the newer version of partclone, we might want to consider disabled checksums to be the default, since we’ve been, in essence, operating without checksums all along.

Added.

I have not added a way to upload your own files. However, I have added a way to define your own file name. All you have to do is upload your own file and point the boot settings to use that new file. The handling for colour and cpair commands are left just as text boxes. You need multiple changes, you just need to enter a new line and type. This leaves potential errors being left unto the users, but should be able to allow more people to make their own color schemes for the boot menu.

Useful links:

http://ipxe.org/cmd/colour
http://ipxe.org/cmd/cpair

of course, I should note, you can, I suppose, inject any ipxe code in these fields, however I doubt that will be much use to others as they’re stilled called only in their relevant functions (get_console/alt_console/host).

@Wayne-Workman I think a moderator could do it. 😄

[quote=“Junkhacker, post: 26662, member: 21583”]if anyone still wanted this, here’s how you get it. add this file to your web-root/fog/lib/hooks folder
Most of the credit goes to Tom and Rowlett on this one.[/quote]

I’m going to modify slightly (so it’s AddHostSerial within the file as well) and push it with the next release if this is okay with you and everybody.

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]

The “Image Size” I’ve been providing is directly how large partclone is reporting the Device Size is. So you would need a drive with at least that size + a little more. There’s no way, for now, to pull all the image size (rec.img.000) size AND (sys.img.000) size, or d1p#.img sizes. It’s not 100% accurate, but should give a fairly good indication of the size needs.

BCD I’m aware of that, but it would mean, image, mount proper drive location, interject the bcd where necessary, and much verification. I’ll try to take time this weekend and test that it works, but it’s no guarantee.

User Management is a goalgoal. I plan to introduce some types of RBAC for users and, maybe later on, groupings of rbacs similar to AD, but less complex.

I don’t have a goals/progress. I’m just a guy who started trying to get the community back up and excited. I’ve been working fairly hard, but I don’t know what all the expectations are. I know the main feature to add before a “stable” release is Windows 8 support. That’s where I’m stuck and I’m sure others are as well.