Quote:
Coudl it be because the disks I'm building are already formatted for the player, and the consumer sofware doesn't allow the use of Hyperterminal?
No, the consumer software allows the use of hyperterminal just fine. It just doesn't let you drop to the shell prompt. But the disk builder software doesn't use the shell. In fact, it engages itself long before the shell prompt even has a chance to be a factor.
The disk builder hooks in at the very first moment the player boots from the protected flash. The protected flash is the boot process that puts up the very first text on the serial port, the "speak now or forever hold your peace..." message. It literally doesn't even get to the point of loading the kernel, let alone any player software on the disk.
I understand your description of how you reproduced this multiple times. It just doesn't make any sense to me: The part of the system that the disk builder connects to is the part that didn't get changed between all of the different things you did.
I can think of only one reason this might happen: If you were trying to apply the disk builder without first pulling the power from the player. To apply the disk builder correctly, you should do things in exactly this order:
- Remove power from the player.
- Run the disk builder.
- Wait until the disk builder prompts you to apply the power.
- Only then do you apply the power.
But even if you didn't do those steps, even if your player was playing music a the time you tried to apply the disk builder, it should (in theory) have rebooted anyway, and still gotten to that protected flash boot. The builder wouldn't even try starting up and wouldn't even reach the pump stage if it hadn't seen that protected flash message. So even then I still don't see how you could have gotten the pump error with Consumer but not Developer.
This is a puzzler.
Previous Topic
Index
