Posted Mom.app -- please help me test
Jerome Vernet
vernet.jerome at wanadoo.fr
Fri Oct 15 13:02:27 MDT 2004
Hi,
The system Folder within my disk image is good, but Mom does'nt want to
boot on this disk. It's working when booting from the CDrom i used to
install.
I try several thing (use bless, use Startem Control Panel within Mom,
etc...)
Here is the log:
Copyright (C) 1997-2004 Samuel Rydh
Starting MOL session 0
*******************************************************
* Measuring the timebase frequency.
* This will take about 5 seconds
*******************************************************
027BA013
027BA019
027BA03B
2004-10-15 20:50:49.597 Mom[1408] In objectValueForTableColumn: row=0
027BA034
027BA035
*******************************************************
* Adding 'timebase_frequency: 0x027BA013' to
* /etc/mol/session.map will prevent this delay
*******************************************************
Locking RAM
Running in PowerPC 7400 mode, 128 MB RAM
Warning: Using hardcoded clock frequency (350 MHz)
Timebase: 41.65 MHz, Bus: 166.62 MHz, Clock: 350 MHz
---> Failed opening '/dev/input/mice': No such file or directory
OHCI USB controller registered
Could not open '/Users/jeromevernet/vms/Test/vmvar/x11.kbd'
Video driver(s): [xvideo]
640* 480, depth 8,32 { 0.0 } Hz
800* 600, depth 8,32 { 0.0 } Hz
1024* 768, depth 8,32 { 0.0 } Hz
1152* 864, depth 8,32 { 0.0 } Hz
1280*1024, depth 8,32 { 0.0 } Hz
1600*1200, depth 8,32 { 0.0 } Hz
CD /dev/disk2s1 CD/DVD <read-only> ------
Disk /Users/jeromev.. - Partioned - <rw> 512 MB
SCSI devices:
<No SCSI Devices>
>> =============================================================
>> Mac-on-Linux OpenFirmware 0.9.70
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> os_seek error
>> --- No bootable disk was found! -----------------------------
>> If this is an oldworld machine, try booting from the MacOS
>> install CD and install MacOS from within MOL.
>> -------------------------------------------------------------
cleaning up...
Terminating threads...
DONE
Le 15 oct. 04, à 17:47, ted bonkenburg a écrit :
> Hi Jerome,
>
> I'm actually not that familiar with OS 9. On OS X, there is a system
> utility called 'bless' [see man bless]. Essentially, this needs to be
> used to set the location of the "System Folder" in the HFS boot block.
> I don't know what the equivalent is for mac os 9.
>
> Why don't you mount the vm's disk image and do bless -info on it and
> post the results? Here is how you would do that:
>
> 1. Make sure Mom is not running and open a terminal
> 2. hdiutil attach <path_to_your_vm>/disk0.dmg
> 3. bless -info /Volumes/<name_of_your_vms_hard_disk_volume>
>
> Perhaps someone knows more about 'bless', but I wouldn't mess with it
> any further at the moment. You could end up accidentally making your
> host system unbootable :-)
>
> Here is an example for my vm:
>
> -----------------------------------------------------------------------
> ---
> tedbook:~ ted$ hdiutil attach ~/vms/rel/disk0.dmg
> Initializing...
> Attaching...
> Finishing...
> Finishing...
> /dev/disk3 Apple_partition_scheme
> /dev/disk3s1 Apple_partition_map
> /dev/disk3s2 Apple_HFS
> /Volumes/untitled
> tedbook:~ ted$ bless -info /Volumes/untitled/
> finderinfo[0]: 30 => Blessed System Folder is
> /Volumes/untitled/System Folder
> finderinfo[1]: 0 => No Startup App folder (ignored anyway)
> finderinfo[2]: 0 => Open-folder linked list empty
> finderinfo[3]: 30 => OS 9 blessed folder is
> /Volumes/untitled/System Folder
> finderinfo[4]: 0 => Unused field unset
> finderinfo[5]: 0 => No OS 9 + X blessed X folder
> 64-bit VSDB volume id: 0x1C49D982A548D68C
> -----------------------------------------------------------------------
> ---
>
> You can see that the System Folder is blessed on my vm. That is
> because I did a proper install, and somewhere along the way the os9
> installation blessed it's virtual disk.
>
> Anyone know how to safely 'bless' a disk image? I'll try to find out
> how and get back to you.
>
> ted
>
> On 15 Oct, 2004, at 3:20 AM, Jérôme VERNET wrote:
>
>> Hi,
>>
>> Just a point from my tests: I was unable to boot from a disk image
>> with a good System Folder. Mom say 'No device to boot'.
>>
>> When I boot from a CD, I can see the virtuel disk within
>> Mol. Selecting with the Startup Panel the System Folder of this disk
>> image as no effect, next time mol is restarted, doesn't want to boot
>> :(
>>
>> Jerome
>> _______________________________________________
>> mol-general mailing list
>> mol-general at lists.maconlinux.org
>> http://lists.maconlinux.org/mailman/listinfo/mol-general
>
> _______________________________________________
> mol-general mailing list
> mol-general at lists.maconlinux.org
> http://lists.maconlinux.org/mailman/listinfo/mol-general
>
More information about the mol-general
mailing list