Re: [B2-devel] [Patch] Use default ROM when ROM path preference is blank

[Alexei S. <ale...@gm...>]

Committed with modifications. I changed the strlen(rom_path) to
*rom_path to make it O(1). Thanks.

-Alexei

On Mon, Aug 24, 2009 at 8:39 PM, Michael Schmitt<msb2ssdev@me> wrote:
> Attached is a patch to SheepShaver, to fix a problem where the ROM file can
> only be found on the first boot.
>
> When a user creates a new SheepShaver machine, there is no preference file,
> so there is not ROM path preference. SheepShaver has logic so that in this
> case, it will look for a ROM file named "ROM" or "Mac OS ROM" in the current
> directory.
>
> The user starts SheepShaver in order to get to the built-in Preferences
> Editor, and changes various settings (such as creation of a hard disk). Then
> the user reboots.
>
> If the user forgot to set the ROM path at this time, then SheepShaver can no
> longer boot. The only recourse is for the user to find and delete the
> preferences file, or use an external preferences editor to set the ROM path.
>
> The fix is to change SheepShaver to use the default ROM names when either
> the rom path is null (no preference) OR an empty string (preference exists
> with no rom path).
>
>
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>
>