Josh Jackson,
>
> > My original idea was automation to save the user configuration settings,
> > but you seem to have the only comment and you're against it. Why not
> > expand the ID in the config file to tell wine something usefull? What data
> > do you want returned by INT 0x13?
> >
>
> How about an optional configuration setting that overrides the automation.
> By default, it's automated and the user has one less thing to learn/worry about with
>the
> configuration. Make it possible to override in case someone finds it useful, and for
>debugging
> purposes
>
Debugging and control. I set a number of my configuration options just to
have control over them so I feel that it would be good to give everybody the
option of taking control.
> > >
> > Give the user the ability to shut off this warning <G>. That would annoy
> > some people a great deal after awhile. Default the warning to ON, but give
> > it an off setting.
>
> The warning could be issued before the RawWrite actually takes place,
> like BIOS virus protection on some systems
>
> maybe set it up as
> BIOS=True, RawWrite, NoWarn
> for those who need it
>
It may also be necessary to pass in some drive parameters. It's not essential
that the drives all be real--they can be virtual. Wine has the ability to use
directories as drives since we can map from the *nix directory tree rather than
actually having hardware from which to read hardware specifics.
> but leave the default setting as
>
> BIOS=True, NoRawWrite
>
> or
>
> BIOS=False
I haven't done this yet because I'm giving the whole group time to look this
over. I'm not big on making changes at the configuration level without giving
fair warning. Besides, I've never done this before. It will be a new
experience.
-Robert 'Admiral' Coeyman
--
http://www.corner.net/admiral/
May you live as long as you wish and age but a single day.
[Telnet to telnet.corner.net]
