dlanor
02-06-2006, 01:34 PM
Many users have reported problems during the startup of myPS2 from HDD, in that the program fails to mount the partition properly. I have made a small investigation of this (by testing, not by source inspection) and found two causes for it.
The primary cause is that the program parses the CONFIG.DAT file erroneously, recognizing only LF (0x0A) but not CR (0x0D) as terminator for the line containing the partition name. This is a bad mistake, as most people will be using a Windows-based text editor to add that line, and most such editors use CR+LF as line terminator by default.
That is why many users report seeing an odd 'half-hidden' character after the last real character of the partition name displayed in the failure message. That odd character is simply how the display routines render the CR character, which the program has tried to use as part of the partition name.
Even after fixing that error, the program still fails to mount that partition for use in its browsers ('My Files' etc). I suspect that this is because a mount point is already in use by the routines that allowed the CONFIG.DAT (and other myPS2 files used at startup) to be read in the first place. But that is still just a speculation on my part, and remains to be proven.
In any case, I assume that both problems will be rather easy to fix.
Best regards: dlanor
The primary cause is that the program parses the CONFIG.DAT file erroneously, recognizing only LF (0x0A) but not CR (0x0D) as terminator for the line containing the partition name. This is a bad mistake, as most people will be using a Windows-based text editor to add that line, and most such editors use CR+LF as line terminator by default.
That is why many users report seeing an odd 'half-hidden' character after the last real character of the partition name displayed in the failure message. That odd character is simply how the display routines render the CR character, which the program has tried to use as part of the partition name.
Even after fixing that error, the program still fails to mount that partition for use in its browsers ('My Files' etc). I suspect that this is because a mount point is already in use by the routines that allowed the CONFIG.DAT (and other myPS2 files used at startup) to be read in the first place. But that is still just a speculation on my part, and remains to be proven.
In any case, I assume that both problems will be rather easy to fix.
Best regards: dlanor