No 32 Bit access under Win95
Phil Leonard
(Wiliam Schneider) writes:
>Installed Windows95 on my machine. When I run the check in hardware it
>tells me that all my drives (2 actual, 2 doublespaced) are using the
>"dos compatable mode" and suggests that there is an entry in my
>config.sys that could be the cause of the problem. I am not running an
>autoexec.bat or config,sys under windows 95.
You are. Autoexec.bat and Config.sys take priority over IO.SYS. Here is a
great post on this subject by Harold from this newsgroup:
*----------------------------------------------------------------------*
Here is a message I E-mailed to Massey (excuse some of it if it
seems too basic):
According to Microsoft, the autoexec.bat and config.sys files are no
longer needed to run Win95. But for backward compatibility, these
files are still present.
By default, when Win95 boots up, the file IO.SYS loads the following
drivers:
HIMEM.SYS, IFSHLP.SYS, SETVER.EXE, DBLSPACE.BIN or DRVSPACE.BIN, &
SHELL=COMMAND.COM
Also the following are loaded into IO.SYS at boot time (with their
default values listed) :
DOS=HIGH,UMB, FILES=60, LASTDRIVE=Z, BUFFERS=30, STACKS=9,256,
FCBS=4, & SHELL=COMMAND.COM /P.
EMM386.EXE is not loaded, so if any of your older DOS programs require
expanded memory, you have to add this to your config.sys file.
The IO.SYS file cannot be edited, so if you want other drivers loaded
or different FILE or BUFFER settings, you would put these in your
config.sys file. Anything added to the config.sys file will take
priority over the IO.SYS file -- as long as the values exceed those
listed in the IO.SYS file (example: FILES=55 in your config.sys file
will be ignored because the IO.SYS has FILES=60).
Smartdrv cache driver (or any other third party cache driver) is no
longer needed in the config.sys or autoexec.bat files as VCACHE takes
it's place. VCACHE is a quicker 32-bit dynamic cache driver and is
loaded by the system registry file. You can look at the cache results,
along with other performance features, using System Monitor in the
Systems Tools Folder.
If you have a CD-ROM drive that operates off a sound card, then the
drivers that were in your autoexec.bat and config.sys files before the
Win95 installation, must remain in the bat and sys files. Win95 uses
the new MSCDEX.EXE to load a CDFS.VxD driver which improves CD-ROM
access and transfer times to your CD-ROM.
Keys to better performance:
Enter the System icon in the control panel folder (in my computer) and
check the Device Manager tab. Then go through each item (double click)
and check the Driver tab (if there is one). Select VxD drivers if there
are any listed then select Apply. This insures you are using the
32-bit protected mode drivers for your windows applications -- which
are quicker than your 16-bit drivers. You can look at the BOOTLOG.TXT
in the C: drive root directory to tell you what has loaded at boot
time.
Also under the System icon, select the Performance tab. Virtual Memory
should be 32-bit and File System should be 32-bit for optimal
performance (File System might say "using other drivers for MS-DOS
compatibility" if your CD-ROM is connected to a sound card). Now under
advance settings -- file system, select Troubleshoot and make sure no
boxes are checked. You can play with the CD-ROM cache, but mine is set
to small.
Under the Advance settings for Virtual Memory, I selected "let windows
manage my settings". This sets up a dynamic virtual memory that
expands and contractes as necessary.
Run Defrag often (on Full Optimization setting) -- this provides much
quicker disk reads and writes.
Here is my config.sys:
DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE NOEMS
BUFFERS=30,0
FILES=60
DOS=UMB
LASTDRIVE=E
FCBS=4,0
DEVICEHIGH /L:1,13984 =C:\TEAC\TEAC_CDA.SYS /D:MSCD001 /P:220 /T:0
DOS=HIGH
I ran memmaker on a MS-DOS mode shutdown to max the conventional memory
for a DOS game that would not run in DOS mode or with a unoptimized
sys and bat files. Before I had 540K conventional memory available for
the game ( which wanted atleast 580K). Now after running memaker, I
have 624K available -- the game runs well and no bad effects with other
windows applications.
Memaker put in the EMM386 command, but if you run memmaker on your
machine and Win95 locks up on reboot with a "windows protected mode
error", memmaker probably put HIGHSCAN in the EMM386 line -- which
should be removed.
My config.sys before memmaker looked like :
DEVICEHIGH /L:1,13984 =C:\TEAC\TEAC_CDA.SYS /D:MSCD001 /P:220 /T:0
DOS=HIGH
*** cdrom driver was needed as I said above.
Every thing ran great except for that one game I told you about.
Here is my autoexec.bat now:
@ECHO OFF
PROMPT $p$g
PATH C:\WINDOWS;C:\WINDOWS\COMMAND;C:\;C:\DOS;C:\UTILITY
PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;C:\QPW\ODAPI;%PATH%
LH /L:1,20960 DFIMCOM
C:\S64D\S64DMODE MONITOR
SET ACAD=C:\ACAD12\SUPPORT;C:\ACAD12\FONTS;C:\ACAD12\ADS
SET ACADCFG=C:\ACAD12
SET ACADDRV=C:\ACAD12\DRV
LH /L:1,56976 C:\WINDOWS\COMMAND\MSCDEX.EXE /D:MSCD001 /M:15
** DFIMCOM is a mouse driver that was required to run Autocad. Normally
a mouse driver is loaded into IO.SYS at boot time but this is the only
program that does not recognized it.
For your config.sys and autoexec.bat files, I would keep everything to
a min. as long as every thing works well. Otherwise use memmaker if a
program needs the conventional memory -- I had QEMM 7.5 but it won't
work with Win95.
Well I hope this helps.
Harold.
*------------------------------------------------------------------------*
>Does anyone have any suggestions?
>I am running standard IDE drives and controller (Not enhanced at this
>point)
Not sure why this would work in WFWG and not in WIN95. According to the
WIN95 WRK Drivespace and Doublespace should work fine with 32dba and
32bfa.
Phil Leonard
an...@ix.netcom.com
Wiliam Schneider
tells me that all my drives (2 actual, 2 doublespaced) are using the
"dos compatable mode" and suggests that there is an entry in my
config.sys that could be the cause of the problem. I am not running an
prior to installing windows and had 32 bit file access with no
problems.
Does anyone have any suggestions?
I am running standard IDE drives and controller (Not enhanced at this
point)
Please reply via Email.
Thx
Red_Hawk
--
Hau Kola
Lakota hemaca
Mitakuye Oyasin
Cetan Lutah
Leonard Grossman
Stacker. How can I tell what 32 bit features I can use and what I can't.
In article <3nueql$g...@ixnews4.ix.netcom.com> an...@ix.netcom.com (Phil
Leonard) writes:>Path:
.....................clip.......................
>Enter the System icon in the control panel folder (in my computer) and
>check the Device Manager tab. Then go through each item (double click)
>and check the Driver tab (if there is one). Select VxD drivers if there
>are any listed then select Apply. This insures you are using the
>32-bit protected mode drivers for your windows applications -- which
>are quicker than your 16-bit drivers. You can look at the BOOTLOG.TXT
>in the C: drive root directory to tell you what has loaded at boot
>time.
>Also under the System icon, select the Performance tab. Virtual Memory
>should be 32-bit and File System should be 32-bit for optimal
>performance (File System might say "using other drivers for MS-DOS
>compatibility" if your CD-ROM is connected to a sound card). Now under
>advance settings -- file system, select Troubleshoot and make sure no
>boxes are checked. You can play with the CD-ROM cache, but mine is set
>to small.
clip......................
Leonard Grossman
gros...@mcs.com Attachments here only.
alternative address:leonard....@syslink.mcs.com
Plug 'n Play has been here for years. Plug it in and play with it until it works....
Alan D Taylor
>
> Enter the System icon in the control panel folder (in my computer) and
> check the Device Manager tab. Then go through each item (double click)
> and check the Driver tab (if there is one). Select VxD drivers if there
> are any listed then select Apply. This insures you are using the
> 32-bit protected mode drivers for your windows applications -- which
> are quicker than your 16-bit drivers. You can look at the BOOTLOG.TXT
> in the C: drive root directory to tell you what has loaded at boot
> time.
>
I'm using 437 Windows 95
===================
I did the above but I didn't see any [Apply] button? For each device with drivers I got a list of them and highlighted the
.vxd one. However, the only button I could select was [OK]. This 'may have' had the desired effect as I was prompted to
'restart the system. Part of the BOOTLOG.TXT is below, however, this seems to show that BOTH standard(16bit) as well
as .vxd(32bit) were loaded. So how do I know what I'm using?
[00003BF9] Dynamic load device sb16.vxd
[00003C02] Dynamic init device SB16
[00003C04] Dynamic init success SB16
[00003C05] Dynamic load success sb16.vxd
[00003C06] Dynamic load device s3.vxd
[00003C0E] Dynamic init device S3
[00003C0F] Dynamic init success S3
[00003C11] Dynamic load success s3.vxd
-----------------------------------------------------------------
Alan D Taylor MBCS, Buckinghamshire, England, UK
al...@adtpc.demon.co.uk
-----------------------------------------------------------------
Harold Pulhug
concerning the Config.sys files and how things are loaded:
> By default, when Win95 boots up, the file IO.SYS loads the following
> drivers:
> HIMEM.SYS, IFSHLP.SYS, SETVER.EXE, DBLSPACE.BIN or DRVSPACE.BIN, &
> SHELL=COMMAND.COM
> Also the following are loaded into IO.SYS at boot time (with their
> default values listed) :
> DOS=HIGH,UMB, FILES=60, LASTDRIVE=Z, BUFFERS=30,
> STACKS=9,256, etc... etc...
Some people who still have problems can look at the information below
*** or *** ( I highly recommend)
reading the Win95 Resource Kit help file found on the Win95 CD-ROM in
the folder: --> Wrk95\Helpfile\95wrk.hlp
Select the "Setup Technical Discussion" and go to "System Startup
Files" --- This is where I received my information from.
The information below was taken from this help file and was what I
condensed in my message to other users:
********************************************************************
Windows 95 uses a new system file, IO.SYS, which replaces the MS-DOS
system files (IO.SYS and MSDOS.SYS). This real-mode operating system
file contains the information needed to start the computer. Your
computer no longer needs CONFIG.SYS and AUTOEXEC.BAT to start the
Windows 95 operating system (although these files are preserved for
backward compatibility with certain applications and drivers).
The drivers loaded by default in IO.SYS include the following:
· HIMEM.SYS
· IFSHLP.SYS
· SETVER.EXE
· DBLSPACE.BIN or DRVSPACE.BIN (if found on the hard disk)
Most of the common functionality provided by the various CONFIG.SYS
file entries are now provided by default in IO.SYS. The following table
lists the common entries in CONFIG.SYS that are now incorporated into
IO.SYS, and shows the default values for Windows 95.
Default CONFIG.SYS Settings Incorporated in Windows 95 IO.SYS
Setting and default Description
dos=high,umb :
Specifies that MS-DOS should be loaded in the high memory area (HMA).
This is the default for Windows 95.
himem.sys :
Enables access to the HMA. This line loads and runs the real-mode
Memory Manager. HIMEM.SYS is loaded by default in Windows 95.
ifshlp.sys :
Installable File System Helper, which loads device drivers. This allows
the system to make file system calls. Until this is loaded, only the
minimal file system from IO.SYS is used. After this point, the full
file system is available.
setver.exe :
Optional TSR-type device. It is included for compatibility reasons.
Some MS-DOS–based applications require a specific version of MS-DOS to
be running. This file responds to applications that query for the
version number and sets the version number required.
files=60 :
Specifies the number of file handle buffers to create. This is
specifically for files opened using MS-DOS calls and is not required by
Windows 95. It is included for compatibility with older applications.
lastdrive=z :
Specifies the last drive letter available for assignment. Again, this
is not required for Windows 95 but is included for compatibility with
older applications. If Windows 95 Setup finds this entry, it is moved
to the Registry.
buffers=30 :
Specifies the number of file buffers to create. This is specifically
for applications using IO.SYS calls and is not required by Windows 95.
stacks=9,256 :
Specifies the number and size of stack frames. This is not required for
Windows 95 but is included for compatibility with older applications.
shell=command.com /p :
Indicates what command process to use. The /p switch indicates that the
command process is permanent and should not be unloaded. If the /p is
not specified in CONFIG.SYS, the command process can be unloaded when
quitting the operating system.
fcbs=4 :
Specifies the number of file control blocks that MS-DOS can have open
at the same time. You should use a fcbs= line in CONFIG.SYS only if you
have an older program that requires such a setting.
To override default values in Windows 95 IO.SYS
Place an entry in CONFIG.SYS with the value you want.
The values in IO.SYS cannot be edited. If CONFIG.SYS contains switches
or other parameters for any of the drivers or settings created by
IO.SYS, the CONFIG.SYS entries override the IO.SYS defaults. Entries
for files=, buffers=, and stacks= must be set in CONFIG.SYS to at least
the default values in IO.SYS.
Note
IO.SYS does not load EMM386.EXE. If any of your applications requires
expanded memory, EMM386 must be defined in CONFIG.SYS. For details
about settings values of emm386=, see Appendix A, “Command-Line
Commands Summary.”
Harold Pulhug
Guy Teague
<del>
: By default, when Win95 boots up, the file IO.SYS loads the following
: HIMEM.SYS, IFSHLP.SYS, SETVER.EXE, DBLSPACE.BIN or DRVSPACE.BIN, &
: SHELL=COMMAND.COM
: Also the following are loaded into IO.SYS at boot time (with their
: default values listed) :
: DOS=HIGH,UMB, FILES=60, LASTDRIVE=Z, BUFFERS=30, STACKS=9,256,
: FCBS=4, & SHELL=COMMAND.COM /P.
: EMM386.EXE is not loaded, so if any of your older DOS programs require
: expanded memory, you have to add this to your config.sys file.
: Here is my config.sys:
: DEVICE=C:\WINDOWS\HIMEM.SYS
^^^^^^^^^
: DEVICE=C:\WINDOWS\EMM386.EXE NOEMS
: BUFFERS=30,0
: FILES=60
: DOS=UMB
^^^^^^^^
: For your config.sys and autoexec.bat files, I would keep everything to
: a min. as long as every thing works well. Otherwise use memmaker if a
: program needs the conventional memory -- I had QEMM 7.5 but it won't
: work with Win95.
: Phil Leonard
: an...@ix.netcom.com
--------
Phil:
I'm not nitpicking -- we're all new and trying to learn. You seem to imply
that Win95 loads himem.sys and dos=umb, but this is not my experience and
in your config.sys file you load them manually. I just checked, and my
Win95 (b347) does _not_ load these lines, I have to do it in my config.sys
also.
My Netroom3, in a _very_ minimal role (no video or sys bios), works with
Win95 and provides some extra (upper) memory, but I'm able to have 639k
using just emm.sys.
I need to run ansi.sys and I'm using the new (32-bit?) version Win95
installed in ../command/. I wonder if you know any way to get Win95 to
load it automatically instead of me using a config.sys line?
TIA
--
Regards, [dteague 73 de "They're out there" -- K. Kesey
Guy @csc.com] KG5VT "Brown shoes don't make it" -- F. Zappa
Murray Morris
>it's place. VCACHE is a quicker 32-bit dynamic cache driver and is
>loaded by the system registry file. You can look at the cache results,
>along with other performance features, using System Monitor in the
>Systems Tools Folder.
Any idea how it dynamically caches? Will it use a certain percentage of
available memory? I liked being able to set a certain amount myself for cache.
-------------
Murray Morris
-------------
Phil Leonard
writes:
>I'm not nitpicking -- we're all new and trying to learn.
That was not my post, I said it was from a member of this group named
Harold Pulhug. Here is a quote of my text:
>H>Autoexec.bat and Config.sys take priority over IO.SYS. Here
>H>is a great post on this subject by Harold from this newsgroup:
>H>*-------------------------------------------------------------------*
>H>Here is a message I E-mailed to Massey (excuse some of it if it
>H>seems too basic):
>I need to run ansi.sys and I'm using the new (32-bit?) version Win95
>installed in ../command/. I wonder if you know any way to get Win95 to
>load it automatically instead of me using a config.sys line?
I don't believe so. I have not figured out ANSI.SYS yet.
Phil Leonard : an...@ix.netcom.com | Free Agent 0.55 : Win95 Beta 4.00.347
Phil Leonard
(Alan D Taylor) writes:
H>> Keys to better performance:
>I'm using 437 Windows 95
>===================
>I did the above but I didn't see any [Apply] button?
That was not my post, I said it was from a member of this group named
Harold Pulhug. Here is a quote of my text:
>H>Autoexec.bat and Config.sys take priority over IO.SYS. Here
>H>is a great post on this subject by Harold from this newsgroup:
>H>*-------------------------------------------------------------------*
>H>Here is a message I E-mailed to Massey (excuse some of it if it
>H>seems too basic):
Phil Leonard
>>it's place. VCACHE is a quicker 32-bit dynamic cache driver and is
>>loaded by the system registry file. You can look at the cache results,
>>along with other performance features, using System Monitor in the
>>Systems Tools Folder.
In article <D81zs...@eskimo.com> mu...@eskimo.com (Murray Morris)
writes:
>Any idea how it dynamically caches? Will it use a certain percentage of
>available memory? I liked being able to set a certain amount myself for >cache.
It uses the available space to make extra virtual memory on demand.
You can limit it's minimum and maximum size, although your are warned
against it.
Gary Price
>Note
>IO.SYS does not load EMM386.EXE. If any of your applications requires
>expanded memory, EMM386 must be defined in CONFIG.SYS. For details
>about settings values of emm386=, see Appendix A, “Command-Line
>Commands Summary.”
Erm, are you sure about that?
I don't have a CONFIG or AUTOEXEC and I get all the expanded I need for
my development software.
I have to confess I haven't read the Appendix A you refer to though.
Regards,
Gary.