Fooling DOS 7.xx (aka win9x) to run win 3.11
Steven V.A.
I have installed on a separate harddisk WFW3.11.
Normally I boot with DOS 6.22 bootdisk, and then load windows.
Booting from my main drive, loads dos 7.xx (win9x). It is impossible
to start win3.11.
I have tried SETVER.EXE, to give "WIN.COM" a 6.22 version number, but
I diden't work.
Any suggestions ?, and thanks in advance !
Greetings,
Steven.
---
A White Sailboat...Raging Waters...A Golden Inca Temple...
And a Great Earthquake...A Giant Condor That Wheels In The Sky...
MCoG ..../// http://www.unity.force9.co.uk/mcog ///
Stephan Grossklass
>
> I have installed on a separate harddisk WFW3.11.
> Normally I boot with DOS 6.22 bootdisk, and then load windows.
>
> Booting from my main drive, loads dos 7.xx (win9x). It is impossible
> to start win3.11.
>
> I have tried SETVER.EXE, to give "WIN.COM" a 6.22 version number, but
> I diden't work.
Get osr2fix.exe. This file contains a fix for MS-DOS 7.10 (Win95OSR2,
Win98, Win98SE) that enables older Windows versions to run.
Stephan
--
Stephan Großklaß (7bit: Grossklass)
eMail: mailto:jgros...@t-online.de | Webmaster: http://www.i24.com/
Home: http://jgrossklass.bei.t-online.de/
P3-500, 128MB, 8+8+19GB HDD; MS-DOS 6.22, WfW 3.11, Calmira II 3.12
James Isaacs
>
> Steven V.A. schrieb:
> >
> > I have installed on a separate harddisk WFW3.11.
> > Normally I boot with DOS 6.22 bootdisk, and then load windows.
> >
> > Booting from my main drive, loads dos 7.xx (win9x). It is impossible
> > to start win3.11.
Rename WIN.COM for Win3.11 to 311.com, or living dangerously incorporate
a routine in you AUTOEXEC.BAT to CALL a batch file that swaps names or
extensions of WIN.COM to WIN.XXX and vice versa.
> >
> > I have tried SETVER.EXE, to give "WIN.COM" a 6.22 version number, but
> > I diden't work.
It is accurately WIN300.BIN not WIN.COM that is the thing you need to
SETVER
>
> Get osr2fix.exe. This file contains a fix for MS-DOS 7.10 (Win95OSR2,
> Win98, Win98SE) that enables older Windows versions to run.
>
> Stephan
My own experience here is that the Fix is imperfect, on a FAT32
partition it nearly always invokes Protected Mode and hard drive errors
on faster/newer systems. My best advice is to follow the method of
Steven V.A.
I would rather that the fix worked on every system, every time, it would
have saved me low level formatting on Friday.
PS to Stephan - every thing you have ever said is golden and true and I
would have been completely lost many times with out your posts here in
the group, grosse Danke!
James Isaacs
Steven V.A.
>Get osr2fix.exe. This file contains a fix for MS-DOS 7.10 (Win95OSR2,
>Win98, Win98SE) that enables older Windows versions to run.
Ok I'll have a loo, I will post the results
Steven V.A.
>It is accurately WIN300.BIN not WIN.COM that is the thing you need to
>SETVER
Sorry, I can't find that file on my HD where win31x is installed :(
Did you mean win386.exe ? thayt's the closest I could find.
>My own experience here is that the Fix is imperfect, on a FAT32
>partition it nearly always invokes Protected Mode and hard drive errors
>on faster/newer systems. My best advice is to follow the method of
>Steven V.A.
Luckily wfw3.11 is installed on a different hard disk ("specimen from
the past" :) so I can try it out safely ....I intend to install all
related software on that drive too.
>I would rather that the fix worked on every system, every time, it would
>have saved me low level formatting on Friday.
That's no fun :(
>PS to Stephan - every thing you have ever said is golden and true and I
>would have been completely lost many times with out your posts here in
>the group, grosse Danke!
Couldn't agree more !
Greetings
Steven
Steven V.A.
>>Get osr2fix.exe. This file contains a fix for MS-DOS 7.10 (Win95OSR2,
>>Win98, Win98SE) that enables older Windows versions to run.
>
>Ok I'll have a loo, I will post the results
^^^
Now, If I learned to type properly :-)
Well, it works. However:
1) I can't enable 32bit disk access
2) sometimes directories look scrambled ( a reboot fixed that - i read
the instructions !)
Note that wfw is placed on a different hd:
C: FAT32 DOS7.xx (aka win98SE)
D: FAT16 WFW3.11
I tought sometimes your hard disk manufactures shipped a special
driver fro that... (?)
Greetings,
Steven
Stephan Grossklass
>
> >>Get osr2fix.exe. This file contains a fix for MS-DOS 7.10 (Win95OSR2,
> >>Win98, Win98SE) that enables older Windows versions to run.
> >
> >Ok I'll have a loo, I will post the results
> ^^^
> Now, If I learned to type properly :-)
Could it be you're not using a fixed pitch font? The underline is at
"wil", not "loo" (where it was obviously intended to be).
> Well, it works. However:
>
> 1) I can't enable 32bit disk access
*wdctrl only supports drives up to 504 MB - replacement FastDisk drivers
support up to 8 GB. But IMHO 32BDA isn't worth the hassle - the gain
resulting from it is usually in the region of zero, sometimes even
negative, plus enabling 32BDA caused COM port troubles here. BTW: Does
32 bit *file* access work?
> 2) sometimes directories look scrambled ( a reboot fixed that - i read
> the instructions !)
Well, I don't have any experience with the DOS 7.1 / WfW combo, so can't
tell you much about that.
> Note that wfw is placed on a different hd:
>
> C: FAT32 DOS7.xx (aka win98SE)
> D: FAT16 WFW3.11
>
> I tought sometimes your hard disk manufactures shipped a special
> driver fro that... (?)
Perhaps you thought of the FastDisk drivers I mentioned?
Steven V.A.
>Could it be you're not using a fixed pitch font? The underline is at
>"wil", not "loo" (where it was obviously intended to be).
It would seem, since over here it looks fine...(on the right place)
>*wdctrl only supports drives up to 504 MB - replacement FastDisk drivers
>support up to 8 GB.
Yes, but it is installed on a HD wich is smaller then 504 MB...so I
suspect there is no limitation.
>But IMHO 32BDA isn't worth the hassle - the gain
>resulting from it is usually in the region of zero, sometimes even
>negative, plus enabling 32BDA caused COM port troubles here. BTW: Does
>32 bit *file* access work?
32 bit file access does actually work :-)
What do you suggest, since my drive does an awful lot of writing and
reading to start a program. Would "smartdrive" make this a bit better
? (it is after all, a disk caching program)
>> 2) sometimes directories look scrambled ( a reboot fixed that - i read
>> the instructions !)
>
>Well, I don't have any experience with the DOS 7.1 / WfW combo, so can't
>tell you much about that.
No damage was done to my data, so no problem..
>Perhaps you thought of the FastDisk drivers I mentioned?
Yes I think I was confused with that.
Thanks for pointing it out.
Greetings,
Steven.
Stephan Grossklass
>
> Stephan Grossklass <sgrossklas...@my-deja.com> wrote:
>
> >Could it be you're not using a fixed pitch font? The underline is at
> >"wil", not "loo" (where it was obviously intended to be).
>
> It would seem, since over here it looks fine...(on the right place)
What font are you using? (Pop up the context menu on the message window;
there's a menu item "Fixed Pitch Font", this should be enabled. A
similar option is available for the compose window, as "Fixed pitch
font" in the Message menu; actually this is also available in Agent's
browser mode.)
> >*wdctrl only supports drives up to 504 MB - replacement FastDisk drivers
> >support up to 8 GB.
>
> Yes, but it is installed on a HD wich is smaller then 504 MB...so I
> suspect there is no limitation.
But your first hard drive is larger than that, isn't it?
> >But IMHO 32BDA isn't worth the hassle - the gain
> >resulting from it is usually in the region of zero, sometimes even
> >negative, plus enabling 32BDA caused COM port troubles here. BTW: Does
> >32 bit *file* access work?
>
> 32 bit file access does actually work :-)
> What do you suggest, since my drive does an awful lot of writing and
> reading to start a program. Would "smartdrive" make this a bit better
> ? (it is after all, a disk caching program)
If 32 bit file access works, a disk cache called VCache, which is much
more efficient than SmartDrive, is already used - if you have plenty of
RAM, I'd suggest 16384 KB as a cache size. Smartdrv is only needed for
floppies and CD-ROM drives. To see which drives are cached by VCache,
open the 386 Enhanced Control Panel applet and click on "Virtual
memory"; then you'll see if the BIOS or a FastDisk driver is used and if
32 bit file access on the various local hard drives is on (32 bit) or
off (16 bit).
Steven V.A.
>What font are you using? (Pop up the context menu on the message window;
>there's a menu item "Fixed Pitch Font", this should be enabled.
I have enabled fixed Pitch font, and I now can see my mistake....
¨¨¨¨¨¨¨¨¨¨¨¨¨
The line under the word enabled should be on the right place.
>But your first hard drive is larger than that, isn't it?
Indeed.
>floppies and CD-ROM drives. To see which drives are cached by VCache,
>open the 386 Enhanced Control Panel applet and click on "Virtual
>memory"; then you'll see if the BIOS or a FastDisk driver is used and if
>32 bit file access on the various local hard drives is on (32 bit) or
>off (16 bit).
Both drives (large and small) say 16bit, using BIOS.
32 bit file acces is checked, 32 bit disk acces is gray.
Anyway I loaded smartdrive. It gave a huge performance jump, so my
problem is (probably) solved.
BTW the system memory (128mb) isn't displayed properly in the "about"
box.
Stephan Grossklass
>
> Stephan Grossklass <sgrossklas...@my-deja.com> wrote:
>
> >What font are you using? (Pop up the context menu on the message window;
> >there's a menu item "Fixed Pitch Font", this should be enabled.
>
> I have enabled fixed Pitch font, and I now can see my mistake....
> ¨¨¨¨¨¨¨¨¨¨¨¨¨
> The line under the word enabled should be on the right place.
Actually, it's under "led fixed Pit". Perhaps you still have to change
the settings for the compose window?
^^^^^^^
("compose" should be underlined)
> Both drives (large and small) say 16bit, using BIOS.
> 32 bit file acces is checked, 32 bit disk acces is gray.
Since none of the drive seems to be using 32BFA, you can disable it.
> Anyway I loaded smartdrive. It gave a huge performance jump, so my
> problem is (probably) solved.
I'd give Smartdrv 8192 KB both for DOS and Windows - it consumes too
much space in the UMBs otherwise. Smartdrv should be loaded *after*
MSCDEX, BTW.
> BTW the system memory (128mb) isn't displayed properly in the "about"
> box.
To use all the memory, you'll need to use himem.sys from MS-DOS 7.0 or
higher (i.e. Windows 95/98). Then the box should display
<available_memory> + <pagefile> - <space_used_by_Windows_and_apps>
Steven V.A.
>Actually, it's under "led fixed Pit". Perhaps you still have to change
>the settings for the compose window?
^^^^^^^
Yes, I forgot to change the compose window <g>
^^^^^^
Change has a line under it.
>Since none of the drive seems to be using 32BFA, you can disable it.
Yes, it diden't make any difference in performance.
>I'd give Smartdrv 8192 KB both for DOS and Windows - it consumes too
>much space in the UMBs otherwise. Smartdrv should be loaded *after*
>MSCDEX, BTW.
OK I'll configure it that way.
>To use all the memory, you'll need to use himem.sys from MS-DOS 7.0 or
>higher (i.e. Windows 95/98). Then the box should display
><available_memory> + <pagefile> - <space_used_by_Windows_and_apps>
I now use Himem of DOS7.1.
So it is logical to see a value that is greater than my total mermory
?
(I believe it said 250 Mb - so this is fine I can suppose)
Outsider
>
>
> If 32 bit file access works, a disk cache called VCache, which is much
> more efficient than SmartDrive, is already used - if you have plenty of
> RAM, I'd suggest 16384 KB as a cache size. Smartdrv is only needed for
> floppies and CD-ROM drives. To see which drives are cached by VCache,
> open the 386 Enhanced Control Panel applet and click on "Virtual
> memory"; then you'll see if the BIOS or a FastDisk driver is used and if
> 32 bit file access on the various local hard drives is on (32 bit) or
> off (16 bit).
>
I have seen this claim made before, but I don't really believe it.
I tried disabling smartdriv and my system ran like a turtle.
--
<!-Outsider//->
MS-DOS 6.22, Windows for Workgroups 3.11, Netscape Communicator 4.08
"The right to be let alone is indeed the beginning of all freedom."
Steven V.A.
>
>I have seen this claim made before, but I don't really believe it.
>I tried disabling smartdriv and my system ran like a turtle.
That's just what I experienced too !
Without smartdrv it would load 2X as long.
(However on a win311 system, where 32disk access and
32BFA were enabled, i did not need smartdrive)
Greetings,
Steven
Stephan Grossklass
>
> Outsider <nonvali...@yahoo.com> wrote:
>
> >I have seen this claim made before, but I don't really believe it.
> >I tried disabling smartdriv and my system ran like a turtle.
>
> That's just what I experienced too !
> Without smartdrv it would load 2X as long.
> (However on a win311 system, where 32disk access and
> 32BFA were enabled, i did not need smartdrive)
To see which drives are *not* cached by VCache, run smartdrv/s in a DOS
box. Here, that's A, B (floppies), R and S (CD-ROM/CD-R). If 32 bit file
access does not work although it should, rmm.d32 may have to be
replaced; otherwise one should check whether ifshlp.sys (WfWg's
ifshlp.sys!) is loaded in cnfig.sys.
Outsider
>
> Outsider <nonvali...@yahoo.com> wrote:
>
> >
> >I have seen this claim made before, but I don't really believe it.
> >I tried disabling smartdriv and my system ran like a turtle.
>
> That's just what I experienced too !
> Without smartdrv it would load 2X as long.
> (However on a win311 system, where 32disk access and
> 32BFA were enabled, i did not need smartdrive)
but previously, it is as I said, with WfW 3.11 and 32BFA and 32BDA.
--
<!-Outsider//->
MS-DOS 6.22, Windows for Workgroups 3.11, Netscape Communicator 4.08
The right to be left alone - the most comprehensive of rights, and the
right most valued by civilized men." --Supreme Justice Louis Brandeis
Steven V.A.
>> That's just what I experienced too !
>> Without smartdrv it would load 2X as long.
>> (However on a win311 system, where 32disk access and
>> 32BFA were enabled, i did not need smartdrive)
>
>If you tell me the steps I will try and duplicate your experience,
>but previously, it is as I said, with WfW 3.11 and 32BFA and 32BDA.
Ok I have WFW3.11 installed on my second HDD (D:)
Using the ORS2Fix program, it let's me start WFW3.11.
Under control panel, 386 enhanced, it says for both drives: 16 bit -
BIOS. OK 'll check the box 32bit file access. Reboot windows. Altough
the box is now checked, it does not make a difference. I cannot mark
the box for 32bit disk acces...
Then, I start smartdrive before wfw 3.11.
Now, there is a big performance jump in disk access.
Greetings,
Steven.
Outsider
>
> Outsider <nonvali...@yahoo.com> wrote:
>
> >> That's just what I experienced too !
> >> Without smartdrv it would load 2X as long.
> >> (However on a win311 system, where 32disk access and
> >> 32BFA were enabled, i did not need smartdrive)
> >
> >If you tell me the steps I will try and duplicate your experience,
> >but previously, it is as I said, with WfW 3.11 and 32BFA and 32BDA.
>
> Ok I have WFW3.11 installed on my second HDD (D:)
> Using the ORS2Fix program, it let's me start WFW3.11.
>
> Under control panel, 386 enhanced, it says for both drives: 16 bit -
> BIOS. OK 'll check the box 32bit file access. Reboot windows. Altough
> the box is now checked, it does not make a difference. I cannot mark
> the box for 32bit disk acces...
>
> Then, I start smartdrive before wfw 3.11.
> Now, there is a big performance jump in disk access.
>
You need a 3rd party driver for 32BDA.
http://home7.inet.tele.dk/batfiles/download/ezdrv203.zip
ezdrv203.zip 287,813 March 12, 1996 freeware
Micro House driver (mh32bit.386) is a direct replacement for Microsoft's 32-Bit
Disk Access
Driver (wdctrl.386), and allows use of IDE drives greater than 528Mbytes in
capacity.
Stephan Grossklass
>
> You need a 3rd party driver for 32BDA.
>
> http://home7.inet.tele.dk/batfiles/download/ezdrv203.zip
> ezdrv203.zip 287,813 March 12, 1996 freeware
> Micro House driver (mh32bit.386) is a direct replacement for Microsoft's 32-Bit
> Disk Access
> Driver (wdctrl.386), and allows use of IDE drives greater than 528Mbytes in
> capacity.
The only problem is that AFAIK he has a 15 GB hard disk, and those
*wdctrl replacements only work with drives up to 8 GB.
Perhaps system.ini, [386Enh], ForceMapper=C helps.
Steven V.A.
>The only problem is that AFAIK he has a 15 GB hard disk, and those
>*wdctrl replacements only work with drives up to 8 GB.
But WFW3.11 is installed on a disk wich is smaller then 500MB...
C: 15 GB (DOS7.10+W98)
D: 170 MB (WFW 3.11)
>Perhaps system.ini, [386Enh], ForceMapper=C helps.
I will try it.