I was about to post bugreport at VirtualBox bugtracker, but decided to
double-check the issue first. On my system floppy images change are
correctly recognized. VirtualBox 4.1.4-3.2.3 OSE OpenSUSE 12.1.
On 16.05.12 19:33, Wolfgang Schechinger wrote:
Dear experts,
I have some floppy images I
I was about to post bugreport at VirtualBox bugtracker, but decided to
double-check the issue first. On my system floppy images change are
correctly recognized. VirtualBox 4.1.4-3.2.3 OSE OpenSUSE 12.1.
The issue is that VirtualBox is not posting diskette media-change
status in the BIOS data
Hi Tom,
thanks for checking the int 13 details on VirtualBox!
I was about to post bugreport at VirtualBox bugtracker, but decided to
double-check the issue first. On my system floppy images change are
correctly recognized. VirtualBox 4.1.4-3.2.3 OSE OpenSUSE 12.1.
The issue is that
I tried using your programs, but for some reason they did not
work. When I loaded the usbprint app, I ran this command
usbprint status and it said on the bottom no printer
installed when I clearly had the printer plugged in. I also
tried it where I loaded it and then plugged in the printer,
Tom:
The issue is that VirtualBox is not posting diskette media-change
status in the BIOS data table.
the 'issue' is that VirtualBox clearly states
'floppy without change-line support'
int13/15 returns '01h floppy without change-line support
int13/16 returns '06h change line active or
Jack,
the 'issue' is that VirtualBox clearly states 'floppy without
change-line support'
int13/15 returns '01h floppy without change-line support int13/16
returns '06h change line active or not supported
but UIDE ignores this, and relies on change line support anyway.
You are WRONG,
Jack,
The issue is that VirtualBox is not posting diskette media-change
status in the BIOS data table.
the 'issue' is that VirtualBox clearly states
'floppy without change-line support'
int13/15 returns '01h floppy without change-line support
int13/16 returns '06h change line active or
Jack-181 wrote:
I will NOT cache a drive which cannot tell me when its media has changed,
and I REFUSE to add all of the
logic in UIDE that Eric notes the DOS kernel contains, to find out if a
media-change has occurred using other methods!
It's not impossible to cache floppies, Jack. You
At 09:22 AM 5/23/2012, Jack wrote:
You are WRONG, Tom!!
Sorry, Jack, but he is not
Honestly Jack, please don't explode each time someone is making a
critical statement. There simply is no reason to get all personal about this...
UIDE has NEVER ignored if a diskette has change-line
UIDE has NEVER ignored if a diskette has change-line support! It
does in fact check the BIOS data table at 0:448h for bit 0 (change
line for diskette A:) or bit 4 (change line for diskette B:). If
those bits are off, diskette A: or diskette B: will not be cached.
if UIDE would check
UIDE has NEVER ignored if a diskette has change-line support! It
does in fact check the BIOS data table at 0:48Fh for bit 0 (change
line for diskette A:) or bit 4 (change line for diskette B:). If
those bits are off, diskette A: or diskette B: will not be cached.
That is an interesting
It's not impossible to cache floppies, Jack. You just need to do it
differently than you're doing now ...
Back in 1980, I told an old friend of mine about a 750K video-driver
package which I had seen (written in C, of course!), and he noted,
They've got GUTS, calling that a DRIVER!
If I had
On Wed, 23 May 2012 09:22:03 Jack ...@earthlink.net wrote :
Subject: Re: [Freedos-user] Virtual floppy change problem
You are WRONG, Tom!!
Is he ? or are you being RUDE, Jack ?
UIDE has NEVER ignored if a diskette has change-line support! It
does in fact check the BIOS data table at
You are WRONG, Tom!!
Is he ? or are you being RUDE, Jack?
Tom could have written me privately, before publicly saying UIDE
assumes change-line support, but did not. I responded in kind!
Not Tom, but I'd like to learn from /what exact source/ you got the
definition for those bits.
My
Jack, PLEASE, don't pull yourself up on the VirtualBox issue, it is
rather a more general problem.
You simply rely on the contents of the memory region rather than than
properly query system via INT13. And that isn't adding much to the
logic and overall size of your drivers compared to the
Eric,
Apologies, I misread my own source file (early!) this morning. UIDE
and UIDE2 check 0:48Fh (not 448h) for the bits that indicate if drive
A: or B: suipport a media-change line. Note the BIOS data lists at:
http://www.bioscentral.com/misc/bda.htm
This document states that bit 0
Given how UIDE/UIDE2's diskette I-O has never been a problem BUT
for VirtualBox, I will keep UIDE/UIDE2 as-is.
this is going nowhere. Jack is right and everybody else is a bloody
idiot.
AMEN
Tom
--
Live Security
At 12:31 PM 5/23/2012, Jack wrote:
As I just got through noting, in another post, why would the BIOS
data include diskette change-line flags if they were NOT intended
to be USED??
Until someone can positively REFUTE the data offered by the BIOS
Central data-table list, my opinion is that neither
As I just got through noting, in another post, why would the BIOS
data include diskette change-line flags if they were NOT intended
to be USED??
Until someone can positively REFUTE the data offered by the BIOS
Central data-table list, my opinion is that neither you nor any-
one else can say
Jack,
Yes, 40:8f might be wrong in VirtualBox and yes the
person who set it to the wrong value may even be in
your BIOS Central style group of 40:8f users. But
for example the IBM PS/2 and PC Technical Reference
(official 1991 IBM docs) clearly describes 40:8f as
RESERVED byte in the BIOS Data
On Wed, 23 May 2012 14:33:00 -0400, Jack gykazequ...@earthlink.net wrote:
Back in 1980, I told an old friend of mine about a 750K video-driver
package which I had seen (written in C, of course!), and he noted,
They've got GUTS, calling that a DRIVER!
Wow, that sounds familiar. Was your
21 matches
Mail list logo
