Andreas Mohr,
>
> Iīve been wasting many thoughts on this and I still donīt know
> how to implement this wine.conf-wise.
> Technically, itīs no problem at all to implement it; the only real
> problem is how to solve the BIOS drive assignment
> (i.e. how to indicate that such-and-such drive can be safely
> written to/read from).
> Perhaps we should just introduce an additional parameter called
> BiosID=XXX for every [Drive X] that says 0x0 and 0x1
> for the floppies and 0x80, ... for the HDDs ?
> Of course the Dev= entry has to be existing for these [Drive X]
> entries in this case...
>
It's a bit easier than that since drives A and B will be the floppies and all
others will be something else. Older systems did have up to 4 floppies, but
those are so rare that I doubt we need to emmulate that configuration.
Whatever's set to drive A and B (when present) will be the floppies. It gets a
bit harder when we have to read type, but I think that could be done.
I was thinking of taking some code from df or fsck to check out how data about
a device is accessed. Maybe there's a header of data somewhere in the system
which wine can access for this information.
> I guess thatīs the way to go.
> Of course that means that itīs each individual userīs own problem if
> he dares to assign a BiosID= for a Drive entry...
> After all it can destroy file systems that way (which often is
> exactly what you want when using int 0x13 functions).
>
Which is definitely a good idea, blame wise. However, I avoided working with
X-Windows for the longest time since the X manuals I have all talk about
monitor damage. It's not that bad, really.
> Again, implementing that should be NO problem at all...
> (a matter of few hours, definitely not days)
>
Once the DOS loader is reparied.
> I guess we could even go as far as print a warning on EVERY
> Wine startup that says something like:
> "Warning ! Wine detected at least one BiosID= entry in your
> config file. This might lead to formatted file systems.
> However, this warning is non-critical; we just want to inform you
> of the implications this setting has."
>
> Simon Harrison, if you want to implement direct device access,
> then just have a look at how I implemented msdos/int25.c and int26.c.
> And get Ralf Brownīs Interrupt List from the net !
>
An ASM programmer without the Interrupt list? <G>.
I'll look at these interrupts. The data I need shouldn't be that hard. I can
make drives A and B default to 1.44 Meg floppies, then pretend that anything
read only is a CD-Rom. Everything else can be a hard drive.
-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]
