sorry now it boots TOO Fast... :D need to add waitdev=4 to kernel line so hardware has a chance to stabilize otherwise if its VMware contact M$ For support. :cry: I have to add that line to my super fast server running on the metal.. That is a common issue.. more details on kernel configs check out...

I use Vmware Workstation 11 for UEFI boot testing. Fatdog64-700b2.iso boot fine directly (in UEFI mode) All works With using USB UEFI stick & booting same iso, I do NOT have working mouse/keyboard once FD is loaded Kingston DataTraveler 108 USB Device Disk ID: {7262287D-571D-4DDD-9837-D1F5E7EC12...

Could you link me to your "redo methodology"

Thanks

sebus

Yes, just realized that it uses reFind on FAT partition in BootImage.img

Boots fine, thanks

sebus

clonezilla-live-20141208-utopic-amd64 (alternative, Ubuntu based) can boot iso in UEFI mode.

Could the same be done for Fatdog64?

Using Vmware Workstation 11 for testing.

Proper /EFI structure is needed for this.

Thanks

sebus

Instead XP use POS2009 Ready, way better!

I see that passing time makes no difference.

Honestly guys, none of you ever used FD in VM using Workstation/Fusion?

Wow! That is (not) the kind of knowledge (or lack of it) one could expect...

OK, so I use the old Fatdog64 521 with kernel 3.03 True Full Install (no initrd involved) But suppose the same would apply to any other version in full install Installation of current tools from Fusion 5.0.2 just fails http://img9.imageshack.us/img9/3519/toolsinstall.png Any ideas how to make it wor...

Jim1911 wrote:Although, xorgwizard does not work, I was able to remove the "nouveau" driver and install the latest NIVIDIA driver.

Did you use Nvidia driver or some .pet?

sebus

But you have to compile it...

I use Fatdog x64 5.21

sebus

First upgrade to current version...

sebus

Don't worry, I am grateful for this really useful front-end app
Keep up the good work!

sebus

Isn't it a front-end and not an app?

sebus

I like VLC, but found Xine being excellent, played everything I thrown at it I would miss it... @Hans, you can sure build VLMC now if you really need it... I hope GLIBC & GCC compiler will be updated, so then I can use MKVToolNix in Fatdog64, as per http://www.murga-linux.com/puppy/viewtopic.php...

Jades wrote:... it would be unlikely I would have managed to salvage much.

Ofcourse you could just copy it to remote machine via network, or to a local USB stick...

sebus

My target is to develop Pburn on the latest official Puppy. I am not the one to decide what burning engine Puppy will provide. Sigmund But the default burning engine is awfully old & buggy I think it would be better to add an option to select what burning engine to use (so user at least can opt...

else #let Pburn define burn engine. cdrtools is prefered if both is present. export CDRECORD="wodim"; export CDDA2WAV="icedax"; export MKISOFS="genisoimage" if which cdrecord > /dev/null 2>&1; then export CDRECORD="cdrecord"; export CDDA2WAV="cdda2wa...

Could a new correct version be build into Fatdog64 on next release?

http://www.murga-linux.com/puppy/viewto ... start=1665

The current one is really OLD

sebus

sebus So, the answer is this; Pburn burns cue-files as long as the backend does. I do not know, but would assume yes (did the actual burn from command line, NOT using pburn). Maybe there should be some version check, otherwise you are fighting something that is not your problem... And at what point...