MOL 0.9.64 on a 6500: report

[Stefan Jeglinski]

>  > though, if I comment out the 2 scsi references in the mol config
>>  file, it boots -without- the debugger  break. I'm more concerned that
>>  mol could cause the debugger break to begin with - is this possibly a
>>  kernel issue rather than a mol issue?
>
>I would guess this is the "AudioCD" bug. When MOL tries to read
>data form an audio CD, the kernel panics (instead of returning
>a sensible error). I used to be able to reproduce this by doing a simple
>"cat /dev/cdrom" as root. I haven't tried it lately though (and not
>all CD players are/were affected).
>
>This bug is one reason why /dev/cdrom is not specified in
>/etc/molrc by default.

You're saying that because the cdrom is scsi, my leaving a blkdev: 
sdX -rw entry is bad because of this bug?

>Yes. I would suggest you use either
>
>	/dev/hda5 -rw -boot
>	/dev/hda9 -rw
>	/dev/hda13 -rw
>or
>	/dev/hda -rw -boot
>
>If you mix, MOL will mount one the same volume twice (one read only,
>and one read/write).

I'll let you know if I see any more funniness.


>Change the resolution in MacOS... The resolution setting in
>/etc/molrc.video has very little effect (basically, it only
>affects the splash screeen).

Thanks.

>Useless output :-). MOL emulates an ADB mouse (not really used
>anymore; MacOS still detects it though) and a USB one. The warning
>just states that someone tried to read from an unimplemented
>ADB mouse registers. This is a completely legal thing to do,
>so the warning just reflects that the fact that MOL implements
>a very basic type of mouse.

OK. BTW, AFAICT you didn't address my observation that I get only 
right-channel sound. Any ideas on this one?


Stefan Jeglinski