Problems with additional RAM aand NIC

Turn off two first lines in config.sys by putting rem in the beginning.
Do you have SCSI CD-ROM? Why there so many SCSI drivers installed?

--
éÇÏÒØ ìÅÊËÏ (Igor Leyko) MS MVP Windows - Shell/User

"Alan" wrote in message
...

"éÇÏÒØ ìÅÊËÏ (Igor Leyko)" wrote in message
...
"Alan" wrote in message
...
Can you post or attach memory resourses list? I suppose System
information
has it or change a view in a device manager for memory resources.
This is what I have just found in the Device Manager for the Rhine
adapter:-
Interrupt Request 03
Memory Range E9000000 - E90000FF
Input/Output Range A800 - A8FF
Memory Range 000D0000 - 000D17FF
This is when it is working OK. I don't have the information for when it
appears to be faulty.

do you have emm386 or any other memory manager in config.sys? Try to
remove
it if yes.

--
éÇÏÒØ ìÅÊËÏ (Igor Leyko) MS MVP Windows - Shell/User


A couple of points. I have copied the Autoexec.bat and Config.sys files
below. I have been browsing the MS Knowledge base and now have some
questions. The path= command, should I have something more specific along
the lines of pointing to the system directory i.e windows/system? (Yes, I
am
running the Resource Kit). Also buried deep down in a MS Dos 6.2 User
Guide
book, it says that when you use EMM386.exe and you have a Network Adapter
installed that uses RAM, you should exclude the memory addresses that the
network adapter uses, so that Windows won't use the same area of memory.
Is
this relevant for Windows 98SE (DOS7) or not and is this what you are
implying by asking me to remove the EMM386 memory manger in the
config.sys.
Finally, with the extra RAM installed and starting in Safe Mode, the
problem
doesn't exist, so yes it must definitely be a Windows problem somewhere.
Alan

SET CTSYN=C:\WINDOWS
@PATH C:\PROGRA~1\WIN98RK;%PATH%
mode con codepage prepare=((850) c:\windows\COMMAND\ega.cpi)
mode con codepage select=850
keyb uk,,c:\windows\COMMAND\keyboard.sys
Set tvdumpflags=8

DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE
device=c:\windows\COMMAND\display.sys con=(ega,,1)
Country=044,850,c:\windows\COMMAND\country.sys
device=c:\rmcd\oakcdrom.sys /D:mscd001
device=c:\rmcd\btdosm.sys
device=c:\rmcd\flashpt.sys
device=c:\rmcd\btcdrom.sys /D:mscd001
device=c:\rmcd\aspi2dos.sys
device=c:\rmcd\aspi8dos.sys
device=c:\rmcd\aspi4dos.sys
device=c:\rmcd\aspi8u2.sys
device=c:\rmcd\aspicd.sys /D:mscd001
device=c:\rmcd\flashpt.sys
files=10
buffers=10
dos=high,umb
stacks=9,256
lastdrive=z

Turn off two first lines in config.sys by putting rem in the beginning.
Do you have SCSI CD-ROM? Why there so many SCSI drivers installed?

--
éÇÏÒØ ìÅÊËÏ (Igor Leyko) MS MVP Windows - Shell/User

"Alan" wrote in message
...

"éÇÏÒØ ìÅÊËÏ (Igor Leyko)" wrote in message
...
"Alan" wrote in message
...
Can you post or attach memory resourses list? I suppose System
information
has it or change a view in a device manager for memory resources.
This is what I have just found in the Device Manager for the Rhine
adapter:-
Interrupt Request 03
Memory Range E9000000 - E90000FF
Input/Output Range A800 - A8FF
Memory Range 000D0000 - 000D17FF
This is when it is working OK. I don't have the information for when it
appears to be faulty.

do you have emm386 or any other memory manager in config.sys? Try to
remove
it if yes.

--
éÇÏÒØ ìÅÊËÏ (Igor Leyko) MS MVP Windows - Shell/User


A couple of points. I have copied the Autoexec.bat and Config.sys files
below. I have been browsing the MS Knowledge base and now have some
questions. The path= command, should I have something more specific along
the lines of pointing to the system directory i.e windows/system? (Yes, I
am
running the Resource Kit). Also buried deep down in a MS Dos 6.2 User
Guide
book, it says that when you use EMM386.exe and you have a Network Adapter
installed that uses RAM, you should exclude the memory addresses that the
network adapter uses, so that Windows won't use the same area of memory.
Is
this relevant for Windows 98SE (DOS7) or not and is this what you are
implying by asking me to remove the EMM386 memory manger in the
config.sys.
Finally, with the extra RAM installed and starting in Safe Mode, the
problem
doesn't exist, so yes it must definitely be a Windows problem somewhere.
Alan

SET CTSYN=C:\WINDOWS
@PATH C:\PROGRA~1\WIN98RK;%PATH%
mode con codepage prepare=((850) c:\windows\COMMAND\ega.cpi)
mode con codepage select=850
keyb uk,,c:\windows\COMMAND\keyboard.sys
Set tvdumpflags=8

DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE
device=c:\windows\COMMAND\display.sys con=(ega,,1)
Country=044,850,c:\windows\COMMAND\country.sys
device=c:\rmcd\oakcdrom.sys /D:mscd001
device=c:\rmcd\btdosm.sys
device=c:\rmcd\flashpt.sys
device=c:\rmcd\btcdrom.sys /D:mscd001
device=c:\rmcd\aspi2dos.sys
device=c:\rmcd\aspi8dos.sys
device=c:\rmcd\aspi4dos.sys
device=c:\rmcd\aspi8u2.sys
device=c:\rmcd\aspicd.sys /D:mscd001
device=c:\rmcd\flashpt.sys
files=10
buffers=10
dos=high,umb
stacks=9,256
lastdrive=z

Ah, ,, with those types of config.sys and autoexec.bat for Win98(SE), your
running in compatibility mode/real mode. Memory is not able to be addressed
properly; devices will not be placed properly in the memory environment;
etc. , e.g. Windows can't "do it's thing" in real mode, or a mixed
real/virtual environment, it is a virtual mode environment.

Memory addressing will be your issues concerning your netcard.. and the
additional ram (last 256) which now needs resource ranges of it's own. {For
a general idea look at the old DOS info regarding emm386 and himem, and
their memory limitations, resource usage, etc.. Then question why your
trying to use them.}

Remove any unnecessary, and preferably all device drivers from config.sys,
except, perhaps, the ones for your specific county/keyboard/video
arrangements, and himem.sys if needed for extended memory with LEGACY DOS
programs (generally games). Though as your using country/keyboard/video
specific settings using emm386.exe would appear advisable.
You could try to loadhigh or devicehigh those drivers you think you need..

To TEST this, rem out the "device=c:\rmcd\(driver)" lines. If no problems
develop, then remove them permanently by creating a copy without them, and
renaming the original to "config.org" or something that you will remember as
being the original (just in case). Then devicehigh the config.sys drivers
you need, and loadhigh (LH) the autoexec.

As for the emm386.exe excludes: yes you can manually exclude the net card
addresses as well as video, but it is generally necessary ONLY when using
real mode drivers. Windows will exclude the addresses if it is necessary
(generally found in the device inf).
Also, your files and buffers (and perhaps stacks) statements would be
considered too small for most modern DOS program usage, and conflicts with
Windows 98 defaults.

So the question is WHY you have all these things in your autoexec and
config in the first place. Do you use DOS mode for something or legacy
devices which require them?
BTW: I haven't seen an autoexec and config like you have SINCE DOS days.
Installing Win95 would have remmed out most of what you have. And since you
asked: info for DOS 6.2(2) is not exactly accurate for 7.0.

FYI: Safe mode does not start normal drivers, just base defaults, hence you
will not find compatibility/real mode drivers causing conflicts when in safe
mode. You could try to "step through" a normal startup, and not loading
config.sys and autoexec.bat to see the effect, Igor can tell you how to do
that.
As for the memory in general, several previous discussions have addressed
the 1 gig problem in 98.. 768 is the sweet spot, 1 gig is iffy at best.

--
MEB
http://peoplescounsel.orgfree.com/

"Most people, sometime in their lives, stumble across truth.
Most jump up, brush themselves off, and hurry on about their business as if
nothing had happen." Winston Churchill
Or to put it another way:
Morpheus can offer you the two pills;
but only you can choose whether you take the red pill or the blue one.
_______________

"Alan" wrote in message
...
|
| "éÇÏÒØ ìÅÊËÏ (Igor Leyko)" wrote in message
| ...
| "Alan" wrote in message
| ...
| Can you post or attach memory resourses list? I suppose System
| information
| has it or change a view in a device manager for memory resources.
| This is what I have just found in the Device Manager for the Rhine
| adapter:-
| Interrupt Request 03
| Memory Range E9000000 - E90000FF
| Input/Output Range A800 - A8FF
| Memory Range 000D0000 - 000D17FF
| This is when it is working OK. I don't have the information for when
it
| appears to be faulty.
|
| do you have emm386 or any other memory manager in config.sys? Try to
| remove
| it if yes.
|
| --
| éÇÏÒØ ìÅÊËÏ (Igor Leyko) MS MVP Windows - Shell/User
|
|
| A couple of points. I have copied the Autoexec.bat and Config.sys files
| below. I have been browsing the MS Knowledge base and now have some
| questions. The path= command, should I have something more specific along
| the lines of pointing to the system directory i.e windows/system? (Yes, I
am
| running the Resource Kit). Also buried deep down in a MS Dos 6.2 User
Guide
| book, it says that when you use EMM386.exe and you have a Network Adapter
| installed that uses RAM, you should exclude the memory addresses that the
| network adapter uses, so that Windows won't use the same area of memory.
Is
| this relevant for Windows 98SE (DOS7) or not and is this what you are
| implying by asking me to remove the EMM386 memory manger in the
config.sys.
| Finally, with the extra RAM installed and starting in Safe Mode, the
problem
| doesn't exist, so yes it must definitely be a Windows problem somewhere.
| Alan
|
| SET CTSYN=C:\WINDOWS
| @PATH C:\PROGRA~1\WIN98RK;%PATH%
| mode con codepage prepare=((850) c:\windows\COMMAND\ega.cpi)
| mode con codepage select=850
| keyb uk,,c:\windows\COMMAND\keyboard.sys
| Set tvdumpflags=8
|
| DEVICE=C:\WINDOWS\HIMEM.SYS
| DEVICE=C:\WINDOWS\EMM386.EXE
| device=c:\windows\COMMAND\display.sys con=(ega,,1)
| Country=044,850,c:\windows\COMMAND\country.sys
| device=c:\rmcd\oakcdrom.sys /D:mscd001
| device=c:\rmcd\btdosm.sys
| device=c:\rmcd\flashpt.sys
| device=c:\rmcd\btcdrom.sys /D:mscd001
| device=c:\rmcd\aspi2dos.sys
| device=c:\rmcd\aspi8dos.sys
| device=c:\rmcd\aspi4dos.sys
| device=c:\rmcd\aspi8u2.sys
| device=c:\rmcd\aspicd.sys /D:mscd001
| device=c:\rmcd\flashpt.sys
| files=10
| buffers=10
| dos=high,umb
| stacks=9,256
| lastdrive=z
|
|
|
|
|

Ah, ,, with those types of config.sys and autoexec.bat for Win98(SE), your
running in compatibility mode/real mode. Memory is not able to be addressed
properly; devices will not be placed properly in the memory environment;
etc. , e.g. Windows can't "do it's thing" in real mode, or a mixed
real/virtual environment, it is a virtual mode environment.

Memory addressing will be your issues concerning your netcard.. and the
additional ram (last 256) which now needs resource ranges of it's own. {For
a general idea look at the old DOS info regarding emm386 and himem, and
their memory limitations, resource usage, etc.. Then question why your
trying to use them.}

Remove any unnecessary, and preferably all device drivers from config.sys,
except, perhaps, the ones for your specific county/keyboard/video
arrangements, and himem.sys if needed for extended memory with LEGACY DOS
programs (generally games). Though as your using country/keyboard/video
specific settings using emm386.exe would appear advisable.
You could try to loadhigh or devicehigh those drivers you think you need..

To TEST this, rem out the "device=c:\rmcd\(driver)" lines. If no problems
develop, then remove them permanently by creating a copy without them, and
renaming the original to "config.org" or something that you will remember as
being the original (just in case). Then devicehigh the config.sys drivers
you need, and loadhigh (LH) the autoexec.

As for the emm386.exe excludes: yes you can manually exclude the net card
addresses as well as video, but it is generally necessary ONLY when using
real mode drivers. Windows will exclude the addresses if it is necessary
(generally found in the device inf).
Also, your files and buffers (and perhaps stacks) statements would be
considered too small for most modern DOS program usage, and conflicts with
Windows 98 defaults.

So the question is WHY you have all these things in your autoexec and
config in the first place. Do you use DOS mode for something or legacy
devices which require them?
BTW: I haven't seen an autoexec and config like you have SINCE DOS days.
Installing Win95 would have remmed out most of what you have. And since you
asked: info for DOS 6.2(2) is not exactly accurate for 7.0.

FYI: Safe mode does not start normal drivers, just base defaults, hence you
will not find compatibility/real mode drivers causing conflicts when in safe
mode. You could try to "step through" a normal startup, and not loading
config.sys and autoexec.bat to see the effect, Igor can tell you how to do
that.
As for the memory in general, several previous discussions have addressed
the 1 gig problem in 98.. 768 is the sweet spot, 1 gig is iffy at best.

--
MEB
http://peoplescounsel.orgfree.com/

"Most people, sometime in their lives, stumble across truth.
Most jump up, brush themselves off, and hurry on about their business as if
nothing had happen." Winston Churchill
Or to put it another way:
Morpheus can offer you the two pills;
but only you can choose whether you take the red pill or the blue one.
_______________

"Alan" wrote in message
...
|
| "éÇÏÒØ ìÅÊËÏ (Igor Leyko)" wrote in message
| ...
| "Alan" wrote in message
| ...
| Can you post or attach memory resourses list? I suppose System
| information
| has it or change a view in a device manager for memory resources.
| This is what I have just found in the Device Manager for the Rhine
| adapter:-
| Interrupt Request 03
| Memory Range E9000000 - E90000FF
| Input/Output Range A800 - A8FF
| Memory Range 000D0000 - 000D17FF
| This is when it is working OK. I don't have the information for when
it
| appears to be faulty.
|
| do you have emm386 or any other memory manager in config.sys? Try to
| remove
| it if yes.
|
| --
| éÇÏÒØ ìÅÊËÏ (Igor Leyko) MS MVP Windows - Shell/User
|
|
| A couple of points. I have copied the Autoexec.bat and Config.sys files
| below. I have been browsing the MS Knowledge base and now have some
| questions. The path= command, should I have something more specific along
| the lines of pointing to the system directory i.e windows/system? (Yes, I
am
| running the Resource Kit). Also buried deep down in a MS Dos 6.2 User
Guide
| book, it says that when you use EMM386.exe and you have a Network Adapter
| installed that uses RAM, you should exclude the memory addresses that the
| network adapter uses, so that Windows won't use the same area of memory.
Is
| this relevant for Windows 98SE (DOS7) or not and is this what you are
| implying by asking me to remove the EMM386 memory manger in the
config.sys.
| Finally, with the extra RAM installed and starting in Safe Mode, the
problem
| doesn't exist, so yes it must definitely be a Windows problem somewhere.
| Alan
|
| SET CTSYN=C:\WINDOWS
| @PATH C:\PROGRA~1\WIN98RK;%PATH%
| mode con codepage prepare=((850) c:\windows\COMMAND\ega.cpi)
| mode con codepage select=850
| keyb uk,,c:\windows\COMMAND\keyboard.sys
| Set tvdumpflags=8
|
| DEVICE=C:\WINDOWS\HIMEM.SYS
| DEVICE=C:\WINDOWS\EMM386.EXE
| device=c:\windows\COMMAND\display.sys con=(ega,,1)
| Country=044,850,c:\windows\COMMAND\country.sys
| device=c:\rmcd\oakcdrom.sys /D:mscd001
| device=c:\rmcd\btdosm.sys
| device=c:\rmcd\flashpt.sys
| device=c:\rmcd\btcdrom.sys /D:mscd001
| device=c:\rmcd\aspi2dos.sys
| device=c:\rmcd\aspi8dos.sys
| device=c:\rmcd\aspi4dos.sys
| device=c:\rmcd\aspi8u2.sys
| device=c:\rmcd\aspicd.sys /D:mscd001
| device=c:\rmcd\flashpt.sys
| files=10
| buffers=10
| dos=high,umb
| stacks=9,256
| lastdrive=z
|
|
|
|
|

First things first, my "Windows knowledge" is self taught. Since early
retirement I have tried to understand various elements of the Windows
software when problems have arisen before making any fixes. (You really miss
tech support when you are at home and something goes wrong!) As a result my
knowledge is patchy to say the least, strong in some areas - weak in others.
The Autoexec and Config sys are as they have evolved over time with this PC,
so if there are errors in the content, please let me know.
Regarding the SCSI drivers, I had problems some time ago trying to use the
CD-ROM from start up and used MS KB article 190303 to resolve it, which it
did. This is where the drivers came from. I haven't had any problems since
then and the drivers do load in MS-DOS. I will try the REM on those entries
later.
Alan
"éÇÏÒØ ìÅÊËÏ (Igor Leyko)" wrote in message
...
Turn off two first lines in config.sys by putting rem in the beginning.
Do you have SCSI CD-ROM? Why there so many SCSI drivers installed?

--
éÇÏÒØ ìÅÊËÏ (Igor Leyko) MS MVP Windows - Shell/User

"Alan" wrote in message
...

"éÇÏÒØ ìÅÊËÏ (Igor Leyko)" wrote in message
...
"Alan" wrote in message
...
Can you post or attach memory resourses list? I suppose System
information
has it or change a view in a device manager for memory resources.
This is what I have just found in the Device Manager for the Rhine
adapter:-
Interrupt Request 03
Memory Range E9000000 - E90000FF
Input/Output Range A800 - A8FF
Memory Range 000D0000 - 000D17FF
This is when it is working OK. I don't have the information for when
it
appears to be faulty.

do you have emm386 or any other memory manager in config.sys? Try to
remove
it if yes.

--
éÇÏÒØ ìÅÊËÏ (Igor Leyko) MS MVP Windows - Shell/User


A couple of points. I have copied the Autoexec.bat and Config.sys files
below. I have been browsing the MS Knowledge base and now have some
questions. The path= command, should I have something more specific
along
the lines of pointing to the system directory i.e windows/system? (Yes,
I
am
running the Resource Kit). Also buried deep down in a MS Dos 6.2 User
Guide
book, it says that when you use EMM386.exe and you have a Network
Adapter
installed that uses RAM, you should exclude the memory addresses that
the
network adapter uses, so that Windows won't use the same area of memory.
Is
this relevant for Windows 98SE (DOS7) or not and is this what you are
implying by asking me to remove the EMM386 memory manger in the
config.sys.
Finally, with the extra RAM installed and starting in Safe Mode, the
problem
doesn't exist, so yes it must definitely be a Windows problem somewhere.
Alan

SET CTSYN=C:\WINDOWS
@PATH C:\PROGRA~1\WIN98RK;%PATH%
mode con codepage prepare=((850) c:\windows\COMMAND\ega.cpi)
mode con codepage select=850
keyb uk,,c:\windows\COMMAND\keyboard.sys
Set tvdumpflags=8

DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE
device=c:\windows\COMMAND\display.sys con=(ega,,1)
Country=044,850,c:\windows\COMMAND\country.sys
device=c:\rmcd\oakcdrom.sys /D:mscd001
device=c:\rmcd\btdosm.sys
device=c:\rmcd\flashpt.sys
device=c:\rmcd\btcdrom.sys /D:mscd001
device=c:\rmcd\aspi2dos.sys
device=c:\rmcd\aspi8dos.sys
device=c:\rmcd\aspi4dos.sys
device=c:\rmcd\aspi8u2.sys
device=c:\rmcd\aspicd.sys /D:mscd001
device=c:\rmcd\flashpt.sys
files=10
buffers=10
dos=high,umb
stacks=9,256
lastdrive=z

First things first, my "Windows knowledge" is self taught. Since early
retirement I have tried to understand various elements of the Windows
software when problems have arisen before making any fixes. (You really miss
tech support when you are at home and something goes wrong!) As a result my
knowledge is patchy to say the least, strong in some areas - weak in others.
The Autoexec and Config sys are as they have evolved over time with this PC,
so if there are errors in the content, please let me know.
Regarding the SCSI drivers, I had problems some time ago trying to use the
CD-ROM from start up and used MS KB article 190303 to resolve it, which it
did. This is where the drivers came from. I haven't had any problems since
then and the drivers do load in MS-DOS. I will try the REM on those entries
later.
Alan
"éÇÏÒØ ìÅÊËÏ (Igor Leyko)" wrote in message
...
Turn off two first lines in config.sys by putting rem in the beginning.
Do you have SCSI CD-ROM? Why there so many SCSI drivers installed?

--
éÇÏÒØ ìÅÊËÏ (Igor Leyko) MS MVP Windows - Shell/User

"Alan" wrote in message
...

"éÇÏÒØ ìÅÊËÏ (Igor Leyko)" wrote in message
...
"Alan" wrote in message
...
Can you post or attach memory resourses list? I suppose System
information
has it or change a view in a device manager for memory resources.
This is what I have just found in the Device Manager for the Rhine
adapter:-
Interrupt Request 03
Memory Range E9000000 - E90000FF
Input/Output Range A800 - A8FF
Memory Range 000D0000 - 000D17FF
This is when it is working OK. I don't have the information for when
it
appears to be faulty.

do you have emm386 or any other memory manager in config.sys? Try to
remove
it if yes.

--
éÇÏÒØ ìÅÊËÏ (Igor Leyko) MS MVP Windows - Shell/User


A couple of points. I have copied the Autoexec.bat and Config.sys files
below. I have been browsing the MS Knowledge base and now have some
questions. The path= command, should I have something more specific
along
the lines of pointing to the system directory i.e windows/system? (Yes,
I
am
running the Resource Kit). Also buried deep down in a MS Dos 6.2 User
Guide
book, it says that when you use EMM386.exe and you have a Network
Adapter
installed that uses RAM, you should exclude the memory addresses that
the
network adapter uses, so that Windows won't use the same area of memory.
Is
this relevant for Windows 98SE (DOS7) or not and is this what you are
implying by asking me to remove the EMM386 memory manger in the
config.sys.
Finally, with the extra RAM installed and starting in Safe Mode, the
problem
doesn't exist, so yes it must definitely be a Windows problem somewhere.
Alan

SET CTSYN=C:\WINDOWS
@PATH C:\PROGRA~1\WIN98RK;%PATH%
mode con codepage prepare=((850) c:\windows\COMMAND\ega.cpi)
mode con codepage select=850
keyb uk,,c:\windows\COMMAND\keyboard.sys
Set tvdumpflags=8

DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE
device=c:\windows\COMMAND\display.sys con=(ega,,1)
Country=044,850,c:\windows\COMMAND\country.sys
device=c:\rmcd\oakcdrom.sys /D:mscd001
device=c:\rmcd\btdosm.sys
device=c:\rmcd\flashpt.sys
device=c:\rmcd\btcdrom.sys /D:mscd001
device=c:\rmcd\aspi2dos.sys
device=c:\rmcd\aspi8dos.sys
device=c:\rmcd\aspi4dos.sys
device=c:\rmcd\aspi8u2.sys
device=c:\rmcd\aspicd.sys /D:mscd001
device=c:\rmcd\flashpt.sys
files=10
buffers=10
dos=high,umb
stacks=9,256
lastdrive=z

"MEB" meb@not wrote in message
...
Ah, ,, with those types of config.sys and autoexec.bat for Win98(SE), your
running in compatibility mode/real mode. Memory is not able to be
addressed
properly; devices will not be placed properly in the memory environment;
etc. , e.g. Windows can't "do it's thing" in real mode, or a mixed
real/virtual environment, it is a virtual mode environment.

Is there anything online that I can browse that explains the above in more
detail?

Memory addressing will be your issues concerning your netcard.. and the
additional ram (last 256) which now needs resource ranges of it's own.
{For
a general idea look at the old DOS info regarding emm386 and himem, and
their memory limitations, resource usage, etc.. Then question why your
trying to use them.}

The netcard is onboard with the MOBO. Any clue where to obtain DOS 7 info?

Remove any unnecessary, and preferably all device drivers from
config.sys,
except, perhaps, the ones for your specific county/keyboard/video
arrangements, and himem.sys if needed for extended memory with LEGACY DOS
programs (generally games). Though as your using country/keyboard/video
specific settings using emm386.exe would appear advisable.
You could try to loadhigh or devicehigh those drivers you think you
need..

Am I correct in assuming, that if I have no legacy DOS requirement I can
remove certain aspects of the autoexec.bat and config.sys? I assume I need
the country/keyboard/video arrangements in autoexec and config sys or is it
better to let windows do its own thing. Again is there anything on line that
I can read to explain what I actually should have in those files?

To TEST this, rem out the "device=c:\rmcd\(driver)" lines. If no problems
develop, then remove them permanently by creating a copy without them, and
renaming the original to "config.org" or something that you will remember
as
being the original (just in case). Then devicehigh the config.sys drivers
you need, and loadhigh (LH) the autoexec.

Can you explain devicehigh loadhigh. The rmcd drivers are installed as per
MS KB article 19303 as I had problems trying to use the CD-ROM in command
prompt mode. How should they be installed then?

As for the emm386.exe excludes: yes you can manually exclude the net card
addresses as well as video, but it is generally necessary ONLY when using
real mode drivers. Windows will exclude the addresses if it is necessary
(generally found in the device inf).
Also, your files and buffers (and perhaps stacks) statements would be
considered too small for most modern DOS program usage, and conflicts with
Windows 98 defaults.

So the question is WHY you have all these things in your autoexec and
config in the first place. Do you use DOS mode for something or legacy
devices which require them?
BTW: I haven't seen an autoexec and config like you have SINCE DOS days.
Installing Win95 would have remmed out most of what you have. And since
you
asked: info for DOS 6.2(2) is not exactly accurate for 7.0.

The PC came pre loaded with 98, which the supplier tech reloaded with 98SE
when the hard drive started to fail and was replaced. I am not knowingly
using DOS mode. ( The creative card makes reference to it in the Device
Manager, but that is disabled). I referred to DOS 6.2.2 as that is the
latest document (user guide) that I have. Again knowledge is weak so I will
be guided.

FYI: Safe mode does not start normal drivers, just base defaults, hence
you
will not find compatibility/real mode drivers causing conflicts when in
safe
mode. You could try to "step through" a normal startup, and not loading
config.sys and autoexec.bat to see the effect, Igor can tell you how to do
that.
As for the memory in general, several previous discussions have addressed
the 1 gig problem in 98.. 768 is the sweet spot, 1 gig is iffy at best.

Thanks for the information.
Alan--
MEB
http://peoplescounsel.orgfree.com/

"Most people, sometime in their lives, stumble across truth.
Most jump up, brush themselves off, and hurry on about their business as
if
nothing had happen." Winston Churchill
Or to put it another way:
Morpheus can offer you the two pills;
but only you can choose whether you take the red pill or the blue one.
_______________

"Alan" wrote in message
...
|
| "éÇÏÒØ ìÅÊËÏ (Igor Leyko)" wrote in message
| ...
| "Alan" wrote in message
| ...
| Can you post or attach memory resourses list? I suppose System
| information
| has it or change a view in a device manager for memory resources.
| This is what I have just found in the Device Manager for the Rhine
| adapter:-
| Interrupt Request 03
| Memory Range E9000000 - E90000FF
| Input/Output Range A800 - A8FF
| Memory Range 000D0000 - 000D17FF
| This is when it is working OK. I don't have the information for when
it
| appears to be faulty.
|
| do you have emm386 or any other memory manager in config.sys? Try to
| remove
| it if yes.
|
| --
| éÇÏÒØ ìÅÊËÏ (Igor Leyko) MS MVP Windows - Shell/User
|
|
| A couple of points. I have copied the Autoexec.bat and Config.sys files
| below. I have been browsing the MS Knowledge base and now have some
| questions. The path= command, should I have something more specific
along
| the lines of pointing to the system directory i.e windows/system? (Yes,
I
am
| running the Resource Kit). Also buried deep down in a MS Dos 6.2 User
Guide
| book, it says that when you use EMM386.exe and you have a Network
Adapter
| installed that uses RAM, you should exclude the memory addresses that
the
| network adapter uses, so that Windows won't use the same area of memory.
Is
| this relevant for Windows 98SE (DOS7) or not and is this what you are
| implying by asking me to remove the EMM386 memory manger in the
config.sys.
| Finally, with the extra RAM installed and starting in Safe Mode, the
problem
| doesn't exist, so yes it must definitely be a Windows problem somewhere.
| Alan
|
| SET CTSYN=C:\WINDOWS
| @PATH C:\PROGRA~1\WIN98RK;%PATH%
| mode con codepage prepare=((850) c:\windows\COMMAND\ega.cpi)
| mode con codepage select=850
| keyb uk,,c:\windows\COMMAND\keyboard.sys
| Set tvdumpflags=8
|
| DEVICE=C:\WINDOWS\HIMEM.SYS
| DEVICE=C:\WINDOWS\EMM386.EXE
| device=c:\windows\COMMAND\display.sys con=(ega,,1)
| Country=044,850,c:\windows\COMMAND\country.sys
| device=c:\rmcd\oakcdrom.sys /D:mscd001
| device=c:\rmcd\btdosm.sys
| device=c:\rmcd\flashpt.sys
| device=c:\rmcd\btcdrom.sys /D:mscd001
| device=c:\rmcd\aspi2dos.sys
| device=c:\rmcd\aspi8dos.sys
| device=c:\rmcd\aspi4dos.sys
| device=c:\rmcd\aspi8u2.sys
| device=c:\rmcd\aspicd.sys /D:mscd001
| device=c:\rmcd\flashpt.sys
| files=10
| buffers=10
| dos=high,umb
| stacks=9,256
| lastdrive=z
|
|
|
|
|

"MEB" meb@not wrote in message
...
Ah, ,, with those types of config.sys and autoexec.bat for Win98(SE), your
running in compatibility mode/real mode. Memory is not able to be
addressed
properly; devices will not be placed properly in the memory environment;
etc. , e.g. Windows can't "do it's thing" in real mode, or a mixed
real/virtual environment, it is a virtual mode environment.

Is there anything online that I can browse that explains the above in more
detail?

Memory addressing will be your issues concerning your netcard.. and the
additional ram (last 256) which now needs resource ranges of it's own.
{For
a general idea look at the old DOS info regarding emm386 and himem, and
their memory limitations, resource usage, etc.. Then question why your
trying to use them.}

The netcard is onboard with the MOBO. Any clue where to obtain DOS 7 info?

Remove any unnecessary, and preferably all device drivers from
config.sys,
except, perhaps, the ones for your specific county/keyboard/video
arrangements, and himem.sys if needed for extended memory with LEGACY DOS
programs (generally games). Though as your using country/keyboard/video
specific settings using emm386.exe would appear advisable.
You could try to loadhigh or devicehigh those drivers you think you
need..

Am I correct in assuming, that if I have no legacy DOS requirement I can
remove certain aspects of the autoexec.bat and config.sys? I assume I need
the country/keyboard/video arrangements in autoexec and config sys or is it
better to let windows do its own thing. Again is there anything on line that
I can read to explain what I actually should have in those files?

To TEST this, rem out the "device=c:\rmcd\(driver)" lines. If no problems
develop, then remove them permanently by creating a copy without them, and
renaming the original to "config.org" or something that you will remember
as
being the original (just in case). Then devicehigh the config.sys drivers
you need, and loadhigh (LH) the autoexec.

Can you explain devicehigh loadhigh. The rmcd drivers are installed as per
MS KB article 19303 as I had problems trying to use the CD-ROM in command
prompt mode. How should they be installed then?

As for the emm386.exe excludes: yes you can manually exclude the net card
addresses as well as video, but it is generally necessary ONLY when using
real mode drivers. Windows will exclude the addresses if it is necessary
(generally found in the device inf).
Also, your files and buffers (and perhaps stacks) statements would be
considered too small for most modern DOS program usage, and conflicts with
Windows 98 defaults.

So the question is WHY you have all these things in your autoexec and
config in the first place. Do you use DOS mode for something or legacy
devices which require them?
BTW: I haven't seen an autoexec and config like you have SINCE DOS days.
Installing Win95 would have remmed out most of what you have. And since
you
asked: info for DOS 6.2(2) is not exactly accurate for 7.0.

The PC came pre loaded with 98, which the supplier tech reloaded with 98SE
when the hard drive started to fail and was replaced. I am not knowingly
using DOS mode. ( The creative card makes reference to it in the Device
Manager, but that is disabled). I referred to DOS 6.2.2 as that is the
latest document (user guide) that I have. Again knowledge is weak so I will
be guided.

FYI: Safe mode does not start normal drivers, just base defaults, hence
you
will not find compatibility/real mode drivers causing conflicts when in
safe
mode. You could try to "step through" a normal startup, and not loading
config.sys and autoexec.bat to see the effect, Igor can tell you how to do
that.
As for the memory in general, several previous discussions have addressed
the 1 gig problem in 98.. 768 is the sweet spot, 1 gig is iffy at best.

Thanks for the information.
Alan--
MEB
http://peoplescounsel.orgfree.com/

"Most people, sometime in their lives, stumble across truth.
Most jump up, brush themselves off, and hurry on about their business as
if
nothing had happen." Winston Churchill
Or to put it another way:
Morpheus can offer you the two pills;
but only you can choose whether you take the red pill or the blue one.
_______________

"Alan" wrote in message
...
|
| "éÇÏÒØ ìÅÊËÏ (Igor Leyko)" wrote in message
| ...
| "Alan" wrote in message
| ...
| Can you post or attach memory resourses list? I suppose System
| information
| has it or change a view in a device manager for memory resources.
| This is what I have just found in the Device Manager for the Rhine
| adapter:-
| Interrupt Request 03
| Memory Range E9000000 - E90000FF
| Input/Output Range A800 - A8FF
| Memory Range 000D0000 - 000D17FF
| This is when it is working OK. I don't have the information for when
it
| appears to be faulty.
|
| do you have emm386 or any other memory manager in config.sys? Try to
| remove
| it if yes.
|
| --
| éÇÏÒØ ìÅÊËÏ (Igor Leyko) MS MVP Windows - Shell/User
|
|
| A couple of points. I have copied the Autoexec.bat and Config.sys files
| below. I have been browsing the MS Knowledge base and now have some
| questions. The path= command, should I have something more specific
along
| the lines of pointing to the system directory i.e windows/system? (Yes,
I
am
| running the Resource Kit). Also buried deep down in a MS Dos 6.2 User
Guide
| book, it says that when you use EMM386.exe and you have a Network
Adapter
| installed that uses RAM, you should exclude the memory addresses that
the
| network adapter uses, so that Windows won't use the same area of memory.
Is
| this relevant for Windows 98SE (DOS7) or not and is this what you are
| implying by asking me to remove the EMM386 memory manger in the
config.sys.
| Finally, with the extra RAM installed and starting in Safe Mode, the
problem
| doesn't exist, so yes it must definitely be a Windows problem somewhere.
| Alan
|
| SET CTSYN=C:\WINDOWS
| @PATH C:\PROGRA~1\WIN98RK;%PATH%
| mode con codepage prepare=((850) c:\windows\COMMAND\ega.cpi)
| mode con codepage select=850
| keyb uk,,c:\windows\COMMAND\keyboard.sys
| Set tvdumpflags=8
|
| DEVICE=C:\WINDOWS\HIMEM.SYS
| DEVICE=C:\WINDOWS\EMM386.EXE
| device=c:\windows\COMMAND\display.sys con=(ega,,1)
| Country=044,850,c:\windows\COMMAND\country.sys
| device=c:\rmcd\oakcdrom.sys /D:mscd001
| device=c:\rmcd\btdosm.sys
| device=c:\rmcd\flashpt.sys
| device=c:\rmcd\btcdrom.sys /D:mscd001
| device=c:\rmcd\aspi2dos.sys
| device=c:\rmcd\aspi8dos.sys
| device=c:\rmcd\aspi4dos.sys
| device=c:\rmcd\aspi8u2.sys
| device=c:\rmcd\aspicd.sys /D:mscd001
| device=c:\rmcd\flashpt.sys
| files=10
| buffers=10
| dos=high,umb
| stacks=9,256
| lastdrive=z
|
|
|
|
|

You have asked for specific information, some of which has been addressed
elsewhere in this news group. As there are at least three issues, this post
is lengthy.

BIG questions require big answers soooooooo...... [don't yell at me for big
post guys, he asked, I deliver, why drag it out, and I did give you credit
where credit due] save this somewhere for future reference.

Relevant Google Search terms would be (heck you could even check on
MICROSOFT, wouldn't that be interesting):

Windows "DOSPRMPT"
Windows "dosstart.bat"
(don't include the quotes; you will find these located in your Windows
directory and can be modified by you for specific use) and
Windows "Exit to DOS"
again not including the quotes; which you can/will create as well.

Also search for:
undocumented DOS

Windows Help contains some basic information (on the START menu). Use the
index to search for MS-DOS.

http://support.microsoft.com/default...;EN-US;q138996
Description of Restarting Computer in MS-DOS Mode
http://support.microsoft.com/?kbid=134400
General Tips for Using MS-DOS Mode
http://support.microsoft.com/?kbid=232915
http://support.microsoft.com/?kbid=188322
http://support.microsoft.com/?kbid=195176
http://www.aumha.org/
http://www.windowshelp.net/ (don't know if this is still around or
relevant, might be .com {memory lapse})
http://www.microsoft.com/technet

HOP over to Microsoft's ftp:
08/27/94 S14710 PD0747.TXT MS-DOS 6.0 Configuration Q&A
05/31/94 S14769 97DOSQA.EXE MSJ 7/94 MS-DOS Q & A
04/07/94 S14707 PD0744.TXT MS-DOS 6.0 General Installation
Q&A
03/22/94 S14666 95DOSQA.EXE MSJ: MS-DOS Q & A
08/16/95 S15494 OLDDOS.EXE MS-DOS Utilities (OLDDOS.EXE)



PCR submitted a master post addressing DOS aspects relating to inability to
exit DOS, though much of that material would be relevant to your questions,
and potential outcome.

From: "PCR"
References: . com







Subject: How to start Win98 after booting in MS-DOS?
Date: Sun, 16 Jul 2006 15:35:29 -0400
Message-ID:
Newsgroups: microsoft.public.win98.gen_discussion
Path: TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
Xref: TK2MSFTNGP01.phx.gbl microsoft.public.win98.gen_discussion:809410

Well, below is the full Master Post, then-- but you're running out! =
Geez!

How you must exit from a Restart to MS-DOS depends upon the Properties =
of "Exit to DOS.pif". Put that string into a Find, INCLUDING the quotes. =
It should be found in C:\Windows. R-Clk it, Properties, Program tab, =
Advanced button-- what is checked & bolted?

Also, "START, Find, *.wos"-- does any show up? It shouldn't!

Here's the Master Post...

A .pif (shortcut to a DOS command) is created when a DOS command is
clicked to execute. Normally, the .pif will be put into the folder of
the command that is clicked. After that, clicking the .pif will execute
the DOS program. You may move it elsewhere. At it's "Properties, Program
tab, Advanced button" it is checked "Suggest MS-DOS Mode as necessary".
C:\Windows\PIF\ is used to hold .pif's that Windows creates when they
cannot be put anywhere else. That happens when you click a DOS app on a
(write protected?) floppy or CD, I believe. It can be troublesome to
have a .pif in there, though.

Much can be done at the Properties tabs of a .pif, including having
Windows reboot to DOS & run off it's private Config.sys & Autoexec.bat
files.

http://support.microsoft.com/default...b;EN-US;151717
Can't EXIT MS-DOS Mode
http://support.microsoft.com/?kbid=3D130448
Can't QUIT MS-DOS Mode
http://support.microsoft.com/default...;EN-US;q138996
Description of Restarting Computer in MS-DOS Mode
http://support.microsoft.com/?kbid=3D134400
General Tips for Using MS-DOS Mode

"Windows 98 Secrets" (Livingston/Straub), pgs 1068,1099, explains:

1. Direct Boot to DOS (Cold booted DOS)

a. Accessed through Boot Menu item, "Command Prompt Only".
b. Windows is not started.
c. Config.sys & Autoexec.bat are run, if present.
d. Ctrl-Alt-Del boots Windows. "WIN" loads Windows.

2. "Quit" to DOS (Re-started MS-DOS mode)

a. Accessed from "START, Shut Down, Re-start in MS-DOS mode", unless
"exit to DOS" pif was converted to "Warm Boot".
b. Accessed from any .pif whose "Properties, Program tab, Advanced
button" is checked "MS-DOS mode" but NOT bolted "Specify a new MS-DOS
configuration".
c. Is NOT a warm boot; Config.sys & Autoexec.bat are NOT re-run, but are
honored to the extent Windows has not mussed the environment they set.
d. Dosstart.bat is run, if present.
e. "EXIT" reloads Windows (from 4K stub), also without a boot.
Ctrl-Alt-Del boots Windows.

3. Warm Booted MS-DOS mode ("Re-boot" to DOS)

a. Accessed from a "Warm Boot" .pif that IS BOTH checked "MS-DOS mode"
AND bolted "Specify a new MS-DOS configuration", in it's Properties,
Program tab, Advanced button.
b. Accessed from START button, if you've altered "exit to dos", as
described.
c. Does a warm boot, using Config.sys and Autoexec.bat as configured in
the pif. (The system files are renamed *.wos & the pif files are
extracted for the session.)
d. Dosstart.bat is NOT run.
e. "EXIT" restores the system Config.sys & Autoexec.bat & warm boots to
Windows. (Ctrl-Alt-Del & "WIN" should NOT be used.)

If you don't want to modify the "exit to dos" pif so that it does a warm
boot, then create a pif this way:

1. "START, Find, Command.com". (Probably in C:\ & C:\Windows).
2. "R-Clk either, Send to, Desktop (create shortcut)". It will be named
"MS-DOS Prompt".
3. R-Clk "MS-DOS Prompt" on the Desktop, & select Properties.
4. Click the Program tab & then the Advanced button.
5. Mark the MS-DOS Mode check box. Mark "Warn before entering..." as
desired.
6. For a "Warm Boot to DOS" pif, mark the "Specify a New MS-DOS
Configuration" button. If you do not do that, you will have a "Quit to
DOS" pif.
7. OK you're way out.

When you click that pif, you will either "warm boot" or "quit to DOS",
depending on what you did in step 6. If it's a warm boot, then the
Config.sys & Autoexec.bat inside the pif are the ones that will be in
effect in your DOS session. Alter them inside the pif as desired, before
clicking it.

Cquirke's WARNING: Because of system/.pif file switching, give a Warm
Boot .pif a chance to execute after clicking. If you click it a second
time before getting to DOS, you may lose your system Config.sys &
Autoexec.bat files.

http://cquirke.mvps.org/9x/doscompat.htm
There are even more DOS mentioned there.

"Select MS-DOS mode on this page", said Leboeuf.
http://www.colba.net/~hlebo49/winmode.htm

Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

"LuckyStrike" om =
wrote in message ...
| Enough to fit that, IF it's smaller than 2 MB's. heh.
|=20
| And IIRC, I *used* to be able to exit MS-DOS (restart in......) by =
typing
| EXIT, then pressing Enter key, but no longer. Must either C-A-D out, =
or else
| use the "WIN /WX" command.
| --=20
|=20
| LuckyStrike
|
| How to make a good newsgroup post:
| http://www.dts-l.org/goodpost.htm
| ------------------------------------------------------------
| "PCR" wrote in message ...
| I have a bigger master post about the various DOS & how to enter & =
exit
| them. How much space do you have left?
|
|
| Thanks or Good Luck,
| There may be humor in this post, and,
| Naturally, you will not sue,
| should things get worse after this,
| PCR
|
| "LuckyStrike" om =
wrote in
| message ...
| | Good info, ..... snipped
| | LS
| | -----------
| |
| | "PCR" wrote in message =
...
| | C:\WIN
| | You are already running Windows.
| |
| | _ Press ALT+ENTER to switch this MS-DOS prompt between
| | windowed and full-screen display.
| | _ Type Exit and press Enter to quit this MS-DOS prompt and
| | return to Windows.
| | _ Press ALT+TAB to switch to Windows or another application.
| |
| | Yea, that's what it says at a Windows DOS in a box prompt. But Glee =
is
| | right. The first thing to try is EXIT, when stuck in DOS...
| |
| | First, try EXIT at the DOS Prompt.
| | If that fails, try "WIN /WX".
| | If that fails, finally...
| |
| | REN C:\Config.sys Config.bad
| | REN C:\Autoexec.bat Autoexec.bad
| | Ctrl-Alt-Del hopefully to Windows, & post the ".bad" files.
| |
| | http://support.microsoft.com/default...b;EN-US;151717
| | Can't EXIT MS-DOS Mode
| | http://support.microsoft.com/?kbid=3D130448
| | Can't QUIT MS-DOS Mode
| | http://support.microsoft.com/default...;EN-US;q138996
| | Description of Restarting Computer in MS-DOS Mode
| |
|| | PCR
| |
| | "LuckyStrike" wrote in message
| ...
| | | Wouldn't you just then get a message stating "You're already in
| Windows"?
| | | LuckyStrike
| | | ------------------------------------------------------------
| | | "jt3" wrote in message
| | | ...
| | | Perhaps not the best way if, say, the person hadn't booted into
| | DOS--i.e.,
| | | I
| | | know your answer is correct, but if the OP didn't know this, =
they
| might
| | | try
| | | that when they'd opened a DOS box . . .
| | | "Brian A." gonefish'n@afarawaylake wrote in message
| | | ...
| | | At the command prompt type: win and press Enter
| | |
| | | Brian A. Sesko { MS MVP_Shell/User }
| | | Conflicts start where information lacks.
| | | http://basconotw.mvps.org/
| | |
| | | How to ask a question: http://support.microsoft.com/kb/555375
| | |
| | |
| | | wrote in message
| | | ups.com...
| | | I accidentally chose to reboot my computer in MS-DOS. I have =
no
| idea
| | | how to get it to boot back up in Win98. I am not a computer
| person
| | | and
| | | have no idea what to type in to get it back to Win98. =
Please
| help!
| | | Thanks.
| | |

FOR THE MEMORY ISSUE:

From: "Curt Christianson"
References:
Subject: Strange memory problem
Date: Thu, 6 Jul 2006 23:05:03 -0500
Message-ID:
Newsgroups: microsoft.public.win98.gen_discussion
Path: TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
Xref: TK2MSFTNGP01.phx.gbl microsoft.public.win98.gen_discussion:808803

Hi Andrea,

This Courtesy of MVP's Bert Kinney, anf Ron Martell:

AM. In reality it will only handle 1 GB of RAM. This will also depend on
hardware installed, in particular the mother board and it's components.
In some cases Win98/ME will function normally with 1.5 GB of RAM.
See the MS KB articles below.

If the system has 384MB's of RAM installed following line can be
added to the [vcache] section of windows\system.ini file.
MaxFileCache=275000

If the system has 512MB's of RAM installed following line can be
added to the [vcache] section of windows\system.ini file.
MaxFileCache=358000

If the system has 700MB's of RAM or more installed following line MUST be
added to the [vcache] section of windows\system.ini file but never more.
MaxFileCache=512000

If you go over 1GB of RAM and still receive errors add the following line
to the [386enh] section of the System.ini file: MaxPhysPage=40000
This limits the amount of physical RAM that Windows can access
to 1GB. If the errors go away with this setting remove the memory over
1GB as it will not be used with this setting.

Windows 95 Can Access Up to Two GB of RAM:
http://support.microsoft.com/support.../q181/5/94.asp

Error Message: Insufficient Memory to Initialize Windows:
http://support.microsoft.com/default...b;EN-US;184447

"Out of Memory" Error Messages with Large Amounts of RAM Installed:
http://support.microsoft.com/support.../Q253/9/12.ASP

Computer May Reboot Continuously with More Than 1.5 GB of RAM:
http://support.microsoft.com/default...b;en-us;304943

Now the question arises, is the increase of RAM going to make my system
faster! Ron Martel [MS MVP] has a technique for determining this.
http://onlinehelp.bc.ca/tips.htm#faster

Regards,
Bert Kinney [MS-MVP DTS]
http://dts-l.org/
****************************************
Free memory testers:
http://www.memtest86.com/
and
DocMemory from:
http://www.simmtester.com/

Curt BD-MVBT

http://dundats.mvps.org/
http://dundats.proboards27.com/index.cgi
http://www.aumha.org/
"Andrea" wrote in message
om...
I've a client with windows 98 installed. All was working fine since I've
installed the antivirus and now a pc with 1GB of ram is unable to open the
DOS shell since memory is finished.

I really don't know ... Any idea? I don't think that the cause could be
the antivirus, because on another client with 256MB of ram, the pc open
and close the dos windows withouth any problems.

Thanks for any reply




AS FOR THE ONLINE INFO for MS-DOS 7.0 check the Microsoft Knowledge base or
TechNet, or if your ready for some "off the wall":
http://www.mdgx.com/
http://en.wikipedia.org/wiki/Main_Page
http://users.aol.com/axcel216/31.htm
http://www.geocities.com/~budallen/dosecrete.html
http://users.aol.com/axcel216/
http://ourworld.compuserve.com/homep...nics/undoc.txt
http://mirror.href.com/thestarman/index.html

NETWORKING/NET CARDS
http://www.practicallynetworked.com
http://www.bcmaven.com/networking/faq.htm
http://www.pcbuyerbeware.co.uk/NetworkingProblems.htm
http://www.homenethelp.com/web/howto/HomeNet-start.asp


IN ANSWER to your general question regarding whether you can remove the
items in config.sys and autoexec.bat related to your country/keyboard/video:
depends on what your doing... but if it's pure dos stuff, then exit to dos
after you create your new exit to DOS pif with those items in the advanced
program setup, and remove them all. Rem out each one, one at a time first
for testing.
If necessary afterwards, go into START/Settings/Control Panel and setup
Windows for your keyboard, display, country specific items.

Windows does not generally need the autoexec or config unless one of your
devices (such as a sound card) has a DOS compatibility aspect, or a program
needs (or thinks it needs) to be included in the PATH statement, or some
indication of it's existence or it's program (autoexec.bat inclusions - such
as anti-virus programs).

On this fully configured (couple hundred programs) and updated 98SE test
computer, my config.sys has nothing in it. Whereas my autoexec.bat has:

C:\PROGRA~1\GRISOFT\AVGFRE~1\BOOTUP.EXE
@echo off
SET BLASTER=A220 I2 D1 T4
LH C:\WINDOWS\ASP4DOS.COM
set temp=c:\temp
set tmp=c:\temp
set pgppath=c:\comp\priv
SET QTJava=C:\WINDOWS\SYSTEM\QTJava.zip
SET CLASSPATH=%QTJava%;
SET TZ=EST5EDT
SET MIDI=SYNTH:1 MAP:E
Path=C:\WINDOWS;C:\WINDOWS\COMMAND;c:\comp;C:\PROG RA~1\ULTRAEDT;


"Alan" wrote in message
...
|
| "MEB" meb@not wrote in message
| ...
| Ah, ,, with those types of config.sys and autoexec.bat for Win98(SE),
your
| running in compatibility mode/real mode. Memory is not able to be
| addressed
| properly; devices will not be placed properly in the memory environment;
| etc. , e.g. Windows can't "do it's thing" in real mode, or a mixed
| real/virtual environment, it is a virtual mode environment.
|
| Is there anything online that I can browse that explains the above in more
| detail?
|
| Memory addressing will be your issues concerning your netcard.. and the
| additional ram (last 256) which now needs resource ranges of it's own.
| {For
| a general idea look at the old DOS info regarding emm386 and himem, and
| their memory limitations, resource usage, etc.. Then question why your
| trying to use them.}
|
| The netcard is onboard with the MOBO. Any clue where to obtain DOS 7 info?
|
| Remove any unnecessary, and preferably all device drivers from
| config.sys,
| except, perhaps, the ones for your specific county/keyboard/video
| arrangements, and himem.sys if needed for extended memory with LEGACY
DOS
| programs (generally games). Though as your using country/keyboard/video
| specific settings using emm386.exe would appear advisable.
| You could try to loadhigh or devicehigh those drivers you think you
| need..
|
| Am I correct in assuming, that if I have no legacy DOS requirement I can
| remove certain aspects of the autoexec.bat and config.sys? I assume I need
| the country/keyboard/video arrangements in autoexec and config sys or is
it
| better to let windows do its own thing. Again is there anything on line
that
| I can read to explain what I actually should have in those files?
|
| To TEST this, rem out the "device=c:\rmcd\(driver)" lines. If no
problems
| develop, then remove them permanently by creating a copy without them,
and
| renaming the original to "config.org" or something that you will
remember
| as
| being the original (just in case). Then devicehigh the config.sys
drivers
| you need, and loadhigh (LH) the autoexec.
|
| Can you explain devicehigh loadhigh. The rmcd drivers are installed as per
| MS KB article 19303 as I had problems trying to use the CD-ROM in command
| prompt mode. How should they be installed then?
|
| As for the emm386.exe excludes: yes you can manually exclude the net
card
| addresses as well as video, but it is generally necessary ONLY when
using
| real mode drivers. Windows will exclude the addresses if it is necessary
| (generally found in the device inf).
| Also, your files and buffers (and perhaps stacks) statements would be
| considered too small for most modern DOS program usage, and conflicts
with
| Windows 98 defaults.
|
| So the question is WHY you have all these things in your autoexec and
| config in the first place. Do you use DOS mode for something or legacy
| devices which require them?
| BTW: I haven't seen an autoexec and config like you have SINCE DOS
days.
| Installing Win95 would have remmed out most of what you have. And since
| you
| asked: info for DOS 6.2(2) is not exactly accurate for 7.0.
|
| The PC came pre loaded with 98, which the supplier tech reloaded with 98SE
| when the hard drive started to fail and was replaced. I am not knowingly
| using DOS mode. ( The creative card makes reference to it in the Device
| Manager, but that is disabled). I referred to DOS 6.2.2 as that is the
| latest document (user guide) that I have. Again knowledge is weak so I
will
| be guided.
|
| FYI: Safe mode does not start normal drivers, just base defaults, hence
| you
| will not find compatibility/real mode drivers causing conflicts when in
| safe
| mode. You could try to "step through" a normal startup, and not loading
| config.sys and autoexec.bat to see the effect, Igor can tell you how to
do
| that.
| As for the memory in general, several previous discussions have
addressed
| the 1 gig problem in 98.. 768 is the sweet spot, 1 gig is iffy at best.
|
| Thanks for the information.
| Alan--
| MEB
| http://peoplescounsel.orgfree.com/
|
|
| "Alan" wrote in message
| ...
| |
| | "éÇÏÒØ ìÅÊËÏ (Igor Leyko)" wrote in message
| | ...
| | "Alan" wrote in message
| | ...
| | Can you post or attach memory resourses list? I suppose System
| | information
| | has it or change a view in a device manager for memory resources.
| | This is what I have just found in the Device Manager for the Rhine
| | adapter:-
| | Interrupt Request 03
| | Memory Range E9000000 - E90000FF
| | Input/Output Range A800 - A8FF
| | Memory Range 000D0000 - 000D17FF
| | This is when it is working OK. I don't have the information for
when
| it
| | appears to be faulty.
| |
| | do you have emm386 or any other memory manager in config.sys? Try to
| | remove
| | it if yes.
| |
| | --
| | éÇÏÒØ ìÅÊËÏ (Igor Leyko) MS MVP Windows - Shell/User
| |
| |
| | A couple of points. I have copied the Autoexec.bat and Config.sys
files
| | below. I have been browsing the MS Knowledge base and now have some
| | questions. The path= command, should I have something more specific
| along
| | the lines of pointing to the system directory i.e windows/system?
(Yes,
| I
| am
| | running the Resource Kit). Also buried deep down in a MS Dos 6.2 User
| Guide
| | book, it says that when you use EMM386.exe and you have a Network
| Adapter
| | installed that uses RAM, you should exclude the memory addresses that
| the
| | network adapter uses, so that Windows won't use the same area of
memory.
| Is
| | this relevant for Windows 98SE (DOS7) or not and is this what you are
| | implying by asking me to remove the EMM386 memory manger in the
| config.sys.
| | Finally, with the extra RAM installed and starting in Safe Mode, the
| problem
| | doesn't exist, so yes it must definitely be a Windows problem
somewhere.
| | Alan
| |
| | SET CTSYN=C:\WINDOWS
| | @PATH C:\PROGRA~1\WIN98RK;%PATH%
| | mode con codepage prepare=((850) c:\windows\COMMAND\ega.cpi)
| | mode con codepage select=850
| | keyb uk,,c:\windows\COMMAND\keyboard.sys
| | Set tvdumpflags=8
| |
| | DEVICE=C:\WINDOWS\HIMEM.SYS
| | DEVICE=C:\WINDOWS\EMM386.EXE
| | device=c:\windows\COMMAND\display.sys con=(ega,,1)
| | Country=044,850,c:\windows\COMMAND\country.sys
| | device=c:\rmcd\oakcdrom.sys /D:mscd001
| | device=c:\rmcd\btdosm.sys
| | device=c:\rmcd\flashpt.sys
| | device=c:\rmcd\btcdrom.sys /D:mscd001
| | device=c:\rmcd\aspi2dos.sys
| | device=c:\rmcd\aspi8dos.sys
| | device=c:\rmcd\aspi4dos.sys
| | device=c:\rmcd\aspi8u2.sys
| | device=c:\rmcd\aspicd.sys /D:mscd001
| | device=c:\rmcd\flashpt.sys
| | files=10
| | buffers=10
| | dos=high,umb
| | stacks=9,256
| | lastdrive=z
| |
| |
| |
| |
| |
|
|
|
--
MEB
http://peoplescounsel.orgfree.com/
BLOG http://peoplescounsel.spaces.live.com/ Public Notice or the "real
world"

"Most people, sometime in their lives, stumble across truth.
Most jump up, brush themselves off, and hurry on about their business as if
nothing had happen." Winston Churchill
Or to put it another way:
Morpheus can offer you the two pills;
but only you can choose whether you take the red pill or the blue one.
_______________

What can I say! There I was thinking a RAM upgrade was just a matter of
putting a VCACHE entry into the System.ini. file and Bob's your uncle! Many
thanks for taking the time and trouble to resource and post all this
information. Needless to say, It will take me a little while to process it
all.
Thanks again.
Alan.

"MEB" meb@not wrote in message
...
You have asked for specific information, some of which has been addressed
elsewhere in this news group. As there are at least three issues, this
post
is lengthy.

BIG questions require big answers soooooooo...... [don't yell at me for
big
post guys, he asked, I deliver, why drag it out, and I did give you credit
where credit due] save this somewhere for future reference.

Relevant Google Search terms would be (heck you could even check on
MICROSOFT, wouldn't that be interesting):

Windows "DOSPRMPT"
Windows "dosstart.bat"
(don't include the quotes; you will find these located in your Windows
directory and can be modified by you for specific use) and
Windows "Exit to DOS"
again not including the quotes; which you can/will create as well.

Also search for:
undocumented DOS

Windows Help contains some basic information (on the START menu). Use the
index to search for MS-DOS.

http://support.microsoft.com/default...;EN-US;q138996
Description of Restarting Computer in MS-DOS Mode
http://support.microsoft.com/?kbid=134400
General Tips for Using MS-DOS Mode
http://support.microsoft.com/?kbid=232915
http://support.microsoft.com/?kbid=188322
http://support.microsoft.com/?kbid=195176
http://www.aumha.org/
http://www.windowshelp.net/ (don't know if this is still around or
relevant, might be .com {memory lapse})
http://www.microsoft.com/technet

HOP over to Microsoft's ftp:
08/27/94 S14710 PD0747.TXT MS-DOS 6.0 Configuration Q&A
05/31/94 S14769 97DOSQA.EXE MSJ 7/94 MS-DOS Q & A
04/07/94 S14707 PD0744.TXT MS-DOS 6.0 General
Installation
Q&A
03/22/94 S14666 95DOSQA.EXE MSJ: MS-DOS Q & A
08/16/95 S15494 OLDDOS.EXE MS-DOS Utilities (OLDDOS.EXE)



PCR submitted a master post addressing DOS aspects relating to inability
to
exit DOS, though much of that material would be relevant to your
questions,
and potential outcome.

From: "PCR"
References: . com







Subject: How to start Win98 after booting in MS-DOS?
Date: Sun, 16 Jul 2006 15:35:29 -0400
Message-ID:
Newsgroups: microsoft.public.win98.gen_discussion
Path: TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
Xref: TK2MSFTNGP01.phx.gbl microsoft.public.win98.gen_discussion:809410

Well, below is the full Master Post, then-- but you're running out! =
Geez!

How you must exit from a Restart to MS-DOS depends upon the Properties =
of "Exit to DOS.pif". Put that string into a Find, INCLUDING the quotes. =
It should be found in C:\Windows. R-Clk it, Properties, Program tab, =
Advanced button-- what is checked & bolted?

Also, "START, Find, *.wos"-- does any show up? It shouldn't!

Here's the Master Post...

A .pif (shortcut to a DOS command) is created when a DOS command is
clicked to execute. Normally, the .pif will be put into the folder of
the command that is clicked. After that, clicking the .pif will execute
the DOS program. You may move it elsewhere. At it's "Properties, Program
tab, Advanced button" it is checked "Suggest MS-DOS Mode as necessary".
C:\Windows\PIF\ is used to hold .pif's that Windows creates when they
cannot be put anywhere else. That happens when you click a DOS app on a
(write protected?) floppy or CD, I believe. It can be troublesome to
have a .pif in there, though.

Much can be done at the Properties tabs of a .pif, including having
Windows reboot to DOS & run off it's private Config.sys & Autoexec.bat
files.

http://support.microsoft.com/default...b;EN-US;151717
Can't EXIT MS-DOS Mode
http://support.microsoft.com/?kbid=3D130448
Can't QUIT MS-DOS Mode
http://support.microsoft.com/default...;EN-US;q138996
Description of Restarting Computer in MS-DOS Mode
http://support.microsoft.com/?kbid=3D134400
General Tips for Using MS-DOS Mode

"Windows 98 Secrets" (Livingston/Straub), pgs 1068,1099, explains:

1. Direct Boot to DOS (Cold booted DOS)

a. Accessed through Boot Menu item, "Command Prompt Only".
b. Windows is not started.
c. Config.sys & Autoexec.bat are run, if present.
d. Ctrl-Alt-Del boots Windows. "WIN" loads Windows.

2. "Quit" to DOS (Re-started MS-DOS mode)

a. Accessed from "START, Shut Down, Re-start in MS-DOS mode", unless
"exit to DOS" pif was converted to "Warm Boot".
b. Accessed from any .pif whose "Properties, Program tab, Advanced
button" is checked "MS-DOS mode" but NOT bolted "Specify a new MS-DOS
configuration".
c. Is NOT a warm boot; Config.sys & Autoexec.bat are NOT re-run, but are
honored to the extent Windows has not mussed the environment they set.
d. Dosstart.bat is run, if present.
e. "EXIT" reloads Windows (from 4K stub), also without a boot.
Ctrl-Alt-Del boots Windows.

3. Warm Booted MS-DOS mode ("Re-boot" to DOS)

a. Accessed from a "Warm Boot" .pif that IS BOTH checked "MS-DOS mode"
AND bolted "Specify a new MS-DOS configuration", in it's Properties,
Program tab, Advanced button.
b. Accessed from START button, if you've altered "exit to dos", as
described.
c. Does a warm boot, using Config.sys and Autoexec.bat as configured in
the pif. (The system files are renamed *.wos & the pif files are
extracted for the session.)
d. Dosstart.bat is NOT run.
e. "EXIT" restores the system Config.sys & Autoexec.bat & warm boots to
Windows. (Ctrl-Alt-Del & "WIN" should NOT be used.)

If you don't want to modify the "exit to dos" pif so that it does a warm
boot, then create a pif this way:

1. "START, Find, Command.com". (Probably in C:\ & C:\Windows).
2. "R-Clk either, Send to, Desktop (create shortcut)". It will be named
"MS-DOS Prompt".
3. R-Clk "MS-DOS Prompt" on the Desktop, & select Properties.
4. Click the Program tab & then the Advanced button.
5. Mark the MS-DOS Mode check box. Mark "Warn before entering..." as
desired.
6. For a "Warm Boot to DOS" pif, mark the "Specify a New MS-DOS
Configuration" button. If you do not do that, you will have a "Quit to
DOS" pif.
7. OK you're way out.

When you click that pif, you will either "warm boot" or "quit to DOS",
depending on what you did in step 6. If it's a warm boot, then the
Config.sys & Autoexec.bat inside the pif are the ones that will be in
effect in your DOS session. Alter them inside the pif as desired, before
clicking it.

Cquirke's WARNING: Because of system/.pif file switching, give a Warm
Boot .pif a chance to execute after clicking. If you click it a second
time before getting to DOS, you may lose your system Config.sys &
Autoexec.bat files.

http://cquirke.mvps.org/9x/doscompat.htm
There are even more DOS mentioned there.

"Select MS-DOS mode on this page", said Leboeuf.
http://www.colba.net/~hlebo49/winmode.htm

Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

"LuckyStrike" om =
wrote in message ...
| Enough to fit that, IF it's smaller than 2 MB's. heh.
|=20
| And IIRC, I *used* to be able to exit MS-DOS (restart in......) by =
typing
| EXIT, then pressing Enter key, but no longer. Must either C-A-D out, =
or else
| use the "WIN /WX" command.
| --=20
|=20
| LuckyStrike
|
| How to make a good newsgroup post:
| http://www.dts-l.org/goodpost.htm
| ------------------------------------------------------------
| "PCR" wrote in message ...
| I have a bigger master post about the various DOS & how to enter & =
exit
| them. How much space do you have left?
|
|
| Thanks or Good Luck,
| There may be humor in this post, and,
| Naturally, you will not sue,
| should things get worse after this,
| PCR
|
| "LuckyStrike" om =
wrote in
| message ...
| | Good info, ..... snipped
| | LS
| | -----------
| |
| | "PCR" wrote in message =
...
| | C:\WIN
| | You are already running Windows.
| |
| | _ Press ALT+ENTER to switch this MS-DOS prompt between
| | windowed and full-screen display.
| | _ Type Exit and press Enter to quit this MS-DOS prompt and
| | return to Windows.
| | _ Press ALT+TAB to switch to Windows or another application.
| |
| | Yea, that's what it says at a Windows DOS in a box prompt. But Glee =
is
| | right. The first thing to try is EXIT, when stuck in DOS...
| |
| | First, try EXIT at the DOS Prompt.
| | If that fails, try "WIN /WX".
| | If that fails, finally...
| |
| | REN C:\Config.sys Config.bad
| | REN C:\Autoexec.bat Autoexec.bad
| | Ctrl-Alt-Del hopefully to Windows, & post the ".bad" files.
| |
| | http://support.microsoft.com/default...b;EN-US;151717
| | Can't EXIT MS-DOS Mode
| | http://support.microsoft.com/?kbid=3D130448
| | Can't QUIT MS-DOS Mode
| | http://support.microsoft.com/default...;EN-US;q138996
| | Description of Restarting Computer in MS-DOS Mode
| |
|| | PCR
| |
| | "LuckyStrike" wrote in message
| ...
| | | Wouldn't you just then get a message stating "You're already in
| Windows"?
| | | LuckyStrike
| | | ------------------------------------------------------------
| | | "jt3" wrote in message
| | | ...
| | | Perhaps not the best way if, say, the person hadn't booted into
| | DOS--i.e.,
| | | I
| | | know your answer is correct, but if the OP didn't know this, =
they
| might
| | | try
| | | that when they'd opened a DOS box . . .
| | | "Brian A." gonefish'n@afarawaylake wrote in message
| | | ...
| | | At the command prompt type: win and press Enter
| | |
| | | Brian A. Sesko { MS MVP_Shell/User }
| | | Conflicts start where information lacks.
| | | http://basconotw.mvps.org/
| | |
| | | How to ask a question: http://support.microsoft.com/kb/555375
| | |
| | |
| | | wrote in message
| | | ups.com...
| | | I accidentally chose to reboot my computer in MS-DOS. I have =
no
| idea
| | | how to get it to boot back up in Win98. I am not a computer
| person
| | | and
| | | have no idea what to type in to get it back to Win98. =
Please
| help!
| | | Thanks.
| | |

FOR THE MEMORY ISSUE:

From: "Curt Christianson"
References:
Subject: Strange memory problem
Date: Thu, 6 Jul 2006 23:05:03 -0500
Message-ID:
Newsgroups: microsoft.public.win98.gen_discussion
Path: TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
Xref: TK2MSFTNGP01.phx.gbl microsoft.public.win98.gen_discussion:808803

Hi Andrea,

This Courtesy of MVP's Bert Kinney, anf Ron Martell:

AM. In reality it will only handle 1 GB of RAM. This will also depend on
hardware installed, in particular the mother board and it's components.
In some cases Win98/ME will function normally with 1.5 GB of RAM.
See the MS KB articles below.

If the system has 384MB's of RAM installed following line can be
added to the [vcache] section of windows\system.ini file.
MaxFileCache=275000

If the system has 512MB's of RAM installed following line can be
added to the [vcache] section of windows\system.ini file.
MaxFileCache=358000

If the system has 700MB's of RAM or more installed following line MUST be
added to the [vcache] section of windows\system.ini file but never
more.
MaxFileCache=512000

If you go over 1GB of RAM and still receive errors add the following line
to the [386enh] section of the System.ini file: MaxPhysPage=40000
This limits the amount of physical RAM that Windows can access
to 1GB. If the errors go away with this setting remove the memory over
1GB as it will not be used with this setting.

Windows 95 Can Access Up to Two GB of RAM:
http://support.microsoft.com/support.../q181/5/94.asp

Error Message: Insufficient Memory to Initialize Windows:
http://support.microsoft.com/default...b;EN-US;184447

"Out of Memory" Error Messages with Large Amounts of RAM Installed:
http://support.microsoft.com/support.../Q253/9/12.ASP

Computer May Reboot Continuously with More Than 1.5 GB of RAM:
http://support.microsoft.com/default...b;en-us;304943

Now the question arises, is the increase of RAM going to make my system
faster! Ron Martel [MS MVP] has a technique for determining this.
http://onlinehelp.bc.ca/tips.htm#faster

Regards,
Bert Kinney [MS-MVP DTS]
http://dts-l.org/
****************************************
Free memory testers:
http://www.memtest86.com/
and
DocMemory from:
http://www.simmtester.com/

Curt BD-MVBT

http://dundats.mvps.org/
http://dundats.proboards27.com/index.cgi
http://www.aumha.org/
"Andrea" wrote in message
om...
I've a client with windows 98 installed. All was working fine since I've
installed the antivirus and now a pc with 1GB of ram is unable to open
the
DOS shell since memory is finished.

I really don't know ... Any idea? I don't think that the cause could be
the antivirus, because on another client with 256MB of ram, the pc open
and close the dos windows withouth any problems.

Thanks for any reply




AS FOR THE ONLINE INFO for MS-DOS 7.0 check the Microsoft Knowledge base
or
TechNet, or if your ready for some "off the wall":
http://www.mdgx.com/
http://en.wikipedia.org/wiki/Main_Page
http://users.aol.com/axcel216/31.htm
http://www.geocities.com/~budallen/dosecrete.html
http://users.aol.com/axcel216/
http://ourworld.compuserve.com/homep...nics/undoc.txt
http://mirror.href.com/thestarman/index.html

NETWORKING/NET CARDS
http://www.practicallynetworked.com
http://www.bcmaven.com/networking/faq.htm
http://www.pcbuyerbeware.co.uk/NetworkingProblems.htm
http://www.homenethelp.com/web/howto/HomeNet-start.asp


IN ANSWER to your general question regarding whether you can remove the
items in config.sys and autoexec.bat related to your
country/keyboard/video:
depends on what your doing... but if it's pure dos stuff, then exit to dos
after you create your new exit to DOS pif with those items in the advanced
program setup, and remove them all. Rem out each one, one at a time first
for testing.
If necessary afterwards, go into START/Settings/Control Panel and setup
Windows for your keyboard, display, country specific items.

Windows does not generally need the autoexec or config unless one of your
devices (such as a sound card) has a DOS compatibility aspect, or a
program
needs (or thinks it needs) to be included in the PATH statement, or some
indication of it's existence or it's program (autoexec.bat inclusions -
such
as anti-virus programs).

On this fully configured (couple hundred programs) and updated 98SE test
computer, my config.sys has nothing in it. Whereas my autoexec.bat has:

C:\PROGRA~1\GRISOFT\AVGFRE~1\BOOTUP.EXE
@echo off
SET BLASTER=A220 I2 D1 T4
LH C:\WINDOWS\ASP4DOS.COM
set temp=c:\temp
set tmp=c:\temp
set pgppath=c:\comp\priv
SET QTJava=C:\WINDOWS\SYSTEM\QTJava.zip
SET CLASSPATH=%QTJava%;
SET TZ=EST5EDT
SET MIDI=SYNTH:1 MAP:E
Path=C:\WINDOWS;C:\WINDOWS\COMMAND;c:\comp;C:\PROG RA~1\ULTRAEDT;


"Alan" wrote in message
...
|
| "MEB" meb@not wrote in message
| ...
| Ah, ,, with those types of config.sys and autoexec.bat for Win98(SE),
your
| running in compatibility mode/real mode. Memory is not able to be
| addressed
| properly; devices will not be placed properly in the memory
environment;
| etc. , e.g. Windows can't "do it's thing" in real mode, or a mixed
| real/virtual environment, it is a virtual mode environment.
|
| Is there anything online that I can browse that explains the above in
more
| detail?
|
| Memory addressing will be your issues concerning your netcard.. and
the
| additional ram (last 256) which now needs resource ranges of it's own.
| {For
| a general idea look at the old DOS info regarding emm386 and himem,
and
| their memory limitations, resource usage, etc.. Then question why your
| trying to use them.}
|
| The netcard is onboard with the MOBO. Any clue where to obtain DOS 7
info?
|
| Remove any unnecessary, and preferably all device drivers from
| config.sys,
| except, perhaps, the ones for your specific county/keyboard/video
| arrangements, and himem.sys if needed for extended memory with LEGACY
DOS
| programs (generally games). Though as your using
country/keyboard/video
| specific settings using emm386.exe would appear advisable.
| You could try to loadhigh or devicehigh those drivers you think you
| need..
|
| Am I correct in assuming, that if I have no legacy DOS requirement I can
| remove certain aspects of the autoexec.bat and config.sys? I assume I
need
| the country/keyboard/video arrangements in autoexec and config sys or is
it
| better to let windows do its own thing. Again is there anything on line
that
| I can read to explain what I actually should have in those files?
|
| To TEST this, rem out the "device=c:\rmcd\(driver)" lines. If no
problems
| develop, then remove them permanently by creating a copy without them,
and
| renaming the original to "config.org" or something that you will
remember
| as
| being the original (just in case). Then devicehigh the config.sys
drivers
| you need, and loadhigh (LH) the autoexec.
|
| Can you explain devicehigh loadhigh. The rmcd drivers are installed as
per
| MS KB article 19303 as I had problems trying to use the CD-ROM in
command
| prompt mode. How should they be installed then?
|
| As for the emm386.exe excludes: yes you can manually exclude the net
card
| addresses as well as video, but it is generally necessary ONLY when
using
| real mode drivers. Windows will exclude the addresses if it is
necessary
| (generally found in the device inf).
| Also, your files and buffers (and perhaps stacks) statements would be
| considered too small for most modern DOS program usage, and conflicts
with
| Windows 98 defaults.
|
| So the question is WHY you have all these things in your autoexec and
| config in the first place. Do you use DOS mode for something or legacy
| devices which require them?
| BTW: I haven't seen an autoexec and config like you have SINCE DOS
days.
| Installing Win95 would have remmed out most of what you have. And
since
| you
| asked: info for DOS 6.2(2) is not exactly accurate for 7.0.
|
| The PC came pre loaded with 98, which the supplier tech reloaded with
98SE
| when the hard drive started to fail and was replaced. I am not knowingly
| using DOS mode. ( The creative card makes reference to it in the Device
| Manager, but that is disabled). I referred to DOS 6.2.2 as that is the
| latest document (user guide) that I have. Again knowledge is weak so I
will
| be guided.
|
| FYI: Safe mode does not start normal drivers, just base defaults,
hence
| you
| will not find compatibility/real mode drivers causing conflicts when
in
| safe
| mode. You could try to "step through" a normal startup, and not
loading
| config.sys and autoexec.bat to see the effect, Igor can tell you how
to
do
| that.
| As for the memory in general, several previous discussions have
addressed
| the 1 gig problem in 98.. 768 is the sweet spot, 1 gig is iffy at
best.
|
| Thanks for the information.
| Alan--
| MEB
| http://peoplescounsel.orgfree.com/
|
|
| "Alan" wrote in message
| ...
| |
| | "éÇÏÒØ ìÅÊËÏ (Igor Leyko)" wrote in message
| | ...
| | "Alan" wrote in message
| | ...
| | Can you post or attach memory resourses list? I suppose System
| | information
| | has it or change a view in a device manager for memory
resources.
| | This is what I have just found in the Device Manager for the
Rhine
| | adapter:-
| | Interrupt Request 03
| | Memory Range E9000000 - E90000FF
| | Input/Output Range A800 - A8FF
| | Memory Range 000D0000 - 000D17FF
| | This is when it is working OK. I don't have the information for
when
| it
| | appears to be faulty.
| |
| | do you have emm386 or any other memory manager in config.sys? Try
to
| | remove
| | it if yes.
| |
| | --
| | éÇÏÒØ ìÅÊËÏ (Igor Leyko) MS MVP Windows - Shell/User
| |
| |
| | A couple of points. I have copied the Autoexec.bat and Config.sys
files
| | below. I have been browsing the MS Knowledge base and now have some
| | questions. The path= command, should I have something more specific
| along
| | the lines of pointing to the system directory i.e windows/system?
(Yes,
| I
| am
| | running the Resource Kit). Also buried deep down in a MS Dos 6.2
User
| Guide
| | book, it says that when you use EMM386.exe and you have a Network
| Adapter
| | installed that uses RAM, you should exclude the memory addresses
that
| the
| | network adapter uses, so that Windows won't use the same area of
memory.
| Is
| | this relevant for Windows 98SE (DOS7) or not and is this what you
are
| | implying by asking me to remove the EMM386 memory manger in the
| config.sys.
| | Finally, with the extra RAM installed and starting in Safe Mode, the
| problem
| | doesn't exist, so yes it must definitely be a Windows problem
somewhere.
| | Alan
| |
| | SET CTSYN=C:\WINDOWS
| | @PATH C:\PROGRA~1\WIN98RK;%PATH%
| | mode con codepage prepare=((850) c:\windows\COMMAND\ega.cpi)
| | mode con codepage select=850
| | keyb uk,,c:\windows\COMMAND\keyboard.sys
| | Set tvdumpflags=8
| |
| | DEVICE=C:\WINDOWS\HIMEM.SYS
| | DEVICE=C:\WINDOWS\EMM386.EXE
| | device=c:\windows\COMMAND\display.sys con=(ega,,1)
| | Country=044,850,c:\windows\COMMAND\country.sys
| | device=c:\rmcd\oakcdrom.sys /D:mscd001
| | device=c:\rmcd\btdosm.sys
| | device=c:\rmcd\flashpt.sys
| | device=c:\rmcd\btcdrom.sys /D:mscd001
| | device=c:\rmcd\aspi2dos.sys
| | device=c:\rmcd\aspi8dos.sys
| | device=c:\rmcd\aspi4dos.sys
| | device=c:\rmcd\aspi8u2.sys
| | device=c:\rmcd\aspicd.sys /D:mscd001
| | device=c:\rmcd\flashpt.sys
| | files=10
| | buffers=10
| | dos=high,umb
| | stacks=9,256
| | lastdrive=z
| |
| |
| |
| |
| |
|
|
|
--
MEB
http://peoplescounsel.orgfree.com/
BLOG http://peoplescounsel.spaces.live.com/ Public Notice or the "real
world"

"Most people, sometime in their lives, stumble across truth.
Most jump up, brush themselves off, and hurry on about their business as
if
nothing had happen." Winston Churchill
Or to put it another way:
Morpheus can offer you the two pills;
but only you can choose whether you take the red pill or the blue one.
_______________