Porteus

I've just tried to install new Porteus-v09 x86_64 (today version) on
FAT32 formatted pendrive, the same which I used for Slax Remix 64bit.
All I got after running bootinst.bat and pressing any key is this error:
http://img811.imageshack.us/img811/6819 ... error1.jpg
("system can't find specified path")

After pressing any key again it gets even worse:
http://img140.imageshack.us/img140/2309 ... error2.jpg

Just letting people know, be careful. I hope it will be fixed...

had a quick look on bootinst.bat and looks ok for me. BackupMbr function was added by Jay, and is executed every time at the end (probably a condition must be there). I have removed 64bit edition from the server - just in case.
Jay should look after it so let's wait on his response.

Thanks for bug report.

Uh oh, I just finished downloading the latest x86_64 image.

Will the fix come in the form of a patch or a new image? (I'm okay with either, I'd just like to know in advance)

new ISO to avoid further confusion

Posted after 21 minute 53 seconds:
EDIT:\\
i was wrong above - BackupMbr function is called only when scrip is run on drive C. For some reason your pendrive letter was not recognized correctly:
"system can't find specified path"
and the script assumed that it's drive C. That's why BackupMbr function was executed, and you got a warning displayed on second screenshot.
Now we need to find out why a proper letter of your usb stick was not recognized correctly...
Any clues?

Only thing i can think of is having more than one USB device plugged in at the time. It seemed to work OK for me during testing although i didn't test with more than one device plugged in. Personally i don't like the method Tomas used to enumerate drives so i will probably rewrite this when i get a chance.

As stated, the backup is initiated when it senses that the C drive is being used. I would say it defaulted there after failing to identify your device. At least the error message stands out!! I think the fix can just be a patch that mounts your ISO, and replaces the bootinst.bat file. Will work it out shortly. In the mean time can you please do some more testing with it and see if you get the same result. The worst it will do is make a backup of your MBR.

Posted after 6 hours 32 minutes 56 seconds:
The problem is a missing semi colon ':' after the first %DISK% in this line

%DISK%\boot\syslinux\syslinux.exe -maf -d \boot\syslinux %DISK%:

Please add the semi colon in and retest. The line should be:

%DISK%:\boot\syslinux\syslinux.exe -maf -d \boot\syslinux %DISK%:

I might also include a new kmenu button in the patch as i prefer blaze's version.

this bug is sorted out now and new ISO is released:
http://ponce.cc/porteus/x86_64/current/ ... x86_64.iso
md5sum is different: 427c273a0ee8b411c13cb6867d6f0a62

please add [Solved]

Posted after 6 hours 32 minutes 56 seconds:
The problem is a missing semi colon ':' after the first %DISK% in this line

%DISK%\boot\syslinux\syslinux.exe -maf -d \boot\syslinux %DISK%: >brokenman

++++++++++++++++++

Psssst ... grammar correction, that's a colon, not a semicolon.

Thought you'd want to know.

There was an old erroneous example in slax, perhaps in bootinst.bat; example was shown telling the script to install to "E:\" -- but it would not work unless you left-off the backslash character.

And I just reinvented another way to screw-up a frugal install -- got the Porteus v1 x86_64 iso and did my usual install -- but it kept reporting that it couldn't find porteus-xx.sgn. The file was obviously there, but the booting kernel script couldn't find it. Turns out that Porteus 64 =is= discerning between upper-case and lower-case characters in filenames on vfat, particularly in the from_dir= statement; I had mixed up a character in my grub4dos menu.lst file.

@burninbush
"Turns out that Porteus 64 =is= discerning between upper-case and lower-case characters in filenames on vfat"
yes, Porteus recognizes capital letters on vfat. in your case it was causing a troubles but it's an advantage in general. For example (if you are using Porteus on 1 PC only) you can put your xorg.conf in
'/porteus/rootcopy/etc/X11' and forget about xconf cheatcode. You will get faster boot then.