!!! What now?? [Solved]

[Ed_P]

On an NTFS partition, sda6, I had two Porteus ISO systems;

Porteus-RazorQT-v2.1-x86_64.iso
Porteus-RazorQT-v3.0-x86_64.iso

along with several other ISOs. The Porteus systems each have their own save.dat file:

/porteussave.dat
/porteus/changes/porteussave.dat

and each system worked independently of the other, except for a shared /porteusmodules folder.

I determine that my Porteus systems need their own partition so I copy everything from sda6 to sda5, another NTFS partition, using my Windows 7 system. I copy folders and files exactly as they were on the sda6 partition.

Porteus 3.0 with it's changes=EXIT:/porteus/changes/porteussave.dat cheatcode works the same as before.

Porteus 2.1 with it's changes=EXIT:/porteussave.dat cheatcode works differently. It doesn't load it's 2.1 /porteussave.dat file, it loads the 3.0 /porteus/changes/porteussave.dat file instead.

Code: Select all

guest@porteus:~$ ./bootmode.sh
quiet from=/ISOs/Porteus-RazorQT-v2.1-x86_64.iso changes=EXIT:/porteussave.dat extramod=/mnt/sda5/porteusmodules 

WHY!!! And how is it doing it and how do I correct it?? I am becoming very leary of this system at this point.

[fanthom]

in 3.0 there was a change in how the 'changes=' cheatcode behaves (now it checks booting media in first place and then searches other devices).
anyway - every person who has multiple porteus installations should use full paths (UUID: recommended) in cheatcodes to avoid troubles.
please read /boot/docs/cheatcodes.txt for details how to use UUID: extension.