Re: [Freedos-user] Virtual floppy change problem with VirtualBox

On Wed, 23 May 2012 14:33:00 -0400, Jack 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 friend Hal Hardenberg b

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

>> 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

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

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 neith

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

> 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

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

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: >> > > This document states th

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

> 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 t

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

At 11:33 AM 5/23/2012, Jack wrote: >And certainly, it is not impossible to cache floppies.Before the >debut of VirtualBox, UIDE/UIDE2 had done so successfully, for years, >without any complaints at all! Jack, PLEASE, don't pull yourself up on the "VirtualBox" issue, it is rather a more genera

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

> to make a long answer short: > in VirtualBox, 40:8f is 00 > again, clearly stating 'change line is not supported' Maybe for your system, obviously not on Wolfgang's, and who-knows re: other "C"-based systems with NO reason to post a BIOS data-table at 0:400! That is my guess re: what is occurr

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

> 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

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

Jack, > 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: > This document states that bit

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

Jack, >>> 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. >> >> i

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

>> 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 inte

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

>> 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 c

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

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 suppor

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

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.

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

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 cha

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

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. > >

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

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

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

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" i

Re: [Freedos-user] Virtual floppy change problem with 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 VirtualBox is not posting diskette media-change > status in the

Re: [Freedos-user] Virtual floppy change problem with 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 VirtualBox is not posting diskette media-change status in the BIOS da

Re: [Freedos-user] Virtual floppy change problem with 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. On 16.05.12 19:33, Wolfgang Schechinger wrote: > Dear experts, > > I have some floppy images

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

Dear STF, I have tried both. No difference. Wo > How did you change the floppy? I mean, did you just choose one > image file after another? Or did you *remove* the current floppy > image *and then* choose the next one? > -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir be

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

How did you change the floppy? I mean, did you just choose one image file after another? Or did you *remove* the current floppy image *and then* choose the next one? -- Live Security Virtual Conference Exclusive liv

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

Wolfgang, > when your harddrive as well as your floppies are virtual: does > it make sense to cache them at all? The host operating system > probably is already caching the relevant data. One cannot be sure the host system is caching data! You should test this, by running with UIDE (caching)

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

Wolfgang, > I don't think that this is possible [using "CC" to flush UIDE's > cache]. In my case, the installation program is asking for the > diskettes one by one, so there is no way to issue a commandline > command in between. You are correct, and I am sorry to hear that. Given the "high lev

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

Jack, when your harddrive as well as your floppies are virtual: does it make sense to cache them at all? The host operating system probably is already caching the relevant data. Wolfgang -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://f

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

Jack, I don't think that this is possible. In my case, the installation prgrams is asking for the disks one by one, so there is no way to issue a commandline command inbetween. Wolfgang -- NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone! Jetzt informie

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

Ulrich, >> UIDE does not include logic to "ignore" a diskette drive. If one >> or two are present, UIDE will always cache them ... > > I think the /B switch works for me. Yes, you are correct -- UIDE is such a complex program that even I "forget" some of its features, from time to time! /B c

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

Wolfgang, > I am so happy that there is something like FreeDos available, even for > free, that I can play around with. As I usually pretty soon run into > very strange challenges for (any) software - some people say, that every > computer that sees me for the first time, simply crashes, si

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

> >>> thanks for the hint! I have commented out the line in autoexec.bat which >>> loads the UIDE.SYS cdrom driver. Now there is no problem accessing the >>> floppy images. >> >> So maybe there is a problem with floppy change signalling >> versus caches - would be interesting to know whether it i

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

me to (temporally) disable the UIDE driver in order to get my stuff done. Wo Original-Nachricht > Datum: Sat, 19 May 2012 14:46:56 -0700 > Von: Jack > An: freedos-user@lists.sourceforge.net > Betreff: Re: [Freedos-user] Virtual floppy change problem with VirtualBox

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

Eric, et al: >> thanks for the hint! I have commented out the line in autoexec.bat which >> loads the UIDE.SYS cdrom driver. Now there is no problem accessing the >> floppy images. > > So maybe there is a problem with floppy change signalling > versus caches - would be interesting to know whether

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

Hi Eric, you mean the option /E ? Still the same. Wolfgang Original-Nachricht > Datum: Sat, 19 May 2012 22:15:22 +0200 > Von: "Eric Auer" > An: freedos-user@lists.sourceforge.net > Betreff: Re: [Freedos-user] Virtual floppy change problem with

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

Hi Wo, > thanks for the hint! I have commented out the line in autoexec.bat which > loads the UIDE.SYS cdrom driver. Now there is no problem accessing the > floppy images. So maybe there is a problem with floppy change signalling versus caches - would be interesting to know whether it is suffici

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

Wolfgang and Ulrich, > Hi Ulrich, > > thanks for the hint! I have commented out the line in autoexec.bat > which loads the UIDE.SYS cdrom driver. Now there is no problem > accessing the floppy images. This sounds to me as if VirtualBox is NOT posting the "media change" bits for a floppy-di

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

Hi Ulrich, thanks for the hint! I have commented out the line in autoexec.bat which loads the UIDE.SYS cdrom driver. Now there is no problem accessing the floppy images. Best regards, Wo -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

Hi Wolfgang, I just tested this with FreeDOS 1.1 as guest and VirtualBox 4.1.14 under OS X as host and it works for me. I start FreeDOS with option 1 in the start menu. I did not load UIDE.SYS in AUTOEXEC.BAT, as I normally don't work with CDs in FreeDOS anyway and VirtualBox conflicts with t

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

- Original-Nachricht > Datum: Wed, 16 May 2012 13:27:59 -0430 > Von: Marco Achury > An: freedos-user@lists.sourceforge.net > Betreff: Re: [Freedos-user] Virtual floppy change problem with VirtualBox > El 16/05/2012 12:03 p.m., Wolfgang Schechinger escribió: > > Dea

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

El 16/05/2012 12:03 p.m., Wolfgang Schechinger escribió: > Dear experts, > > I have some floppy images I want to use with FreeDos that is running in a VM > (VirtualBox). The images work fine with e.g. Windows in such an environment. > > However with the virtual FreeDos, disk changes are not recog

[Freedos-user] Virtual floppy change problem with VirtualBox

Dear experts, I have some floppy images I want to use with FreeDos that is running in a VM (VirtualBox). The images work fine with e.g. Windows in such an environment. However with the virtual FreeDos, disk changes are not recognized: Only the first Image that has been used after boot is show