VFAT

No luck again!

Here is the spower.bat: @c:\dosboot\pcifind 0x6306 0x1039
@if errorlevel 1 c:\windows\system\setpower.exe





"PCR" wrote:

| Let us see that "sPower.bat". After it passes muster, try a boot with
| the changes above. Then, try with "sPower" deactivated by unchecking
it
| at "START button, Run, MSConfig, Startup tab". However, you must
double
| check that it does not turn itself back on!

Autoexec.bat tab, that is.

"PCR" wrote in message
...
....snip

No luck so far!

Here is the spower.bat: @c:\dosboot\pcifind 0x6306 0x1039
@if errorlevel 1
c:\windows\system\setpower.exe

Also did not realize I left out a few lines at the end of my autoexec.bat.
My apologizies, here it is:

@ECHO OFF
SET BLASTER=A220 I7 D1 H5 P330 T6

REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

path C:\WINDOWS;C:\WINDOWS\COMMAND

rem sPower will initialize the USB Keyboard in DOS.

call c:\dosboot\sPower


Rem TShoot: if not exist c:\blocks\ml.txt CALL
c:\windows\temp\Colour\FrstBoot.bat
rem if not exist c:\blocks\ml.txt CALL c:\windows\temp\Colour\FrstBoot.bat
call c:\dosboot\drivers.bat

Rem TShoot: rem - By Windows Setup - mscdex.exe /d:IDECD000 /L:M
- By Windows Setup - mscdex.exe /d:IDECD000 /L:M
call c:\hp\specials\initial

Set tvdumpflags=10

SET PATH=%PATH%;C:\PROGRA~1\ATITEC~1\ATICON~1



Here is what I have tried based on your suggestions:

1. entered new config.sys. rebooted, VFAT error

2. removed the dulplicate spower line in autoexec.bat
put rem in front of other one (rem spower will initialize......)
rebooted, vfat error

3. Placed rem in front of the call c:\dosboot\sPower line in autoexec.bat &
left rem placed in item 2 above. rebooted, vfat error





"PCR" wrote:

| Let us see that "sPower.bat". After it passes muster, try a boot with
| the changes above. Then, try with "sPower" deactivated by unchecking
it
| at "START button, Run, MSConfig, Startup tab". However, you must
double
| check that it does not turn itself back on!

Autoexec.bat tab, that is.

"PCR" wrote in message
...
....snip

Rereading an earlier post of yours, you said...

"Further troubleshooting has found that the card works and all is well
if I bypass the config.sys during boot."

....Did you mean JUST Config.sys & not Autoexec.bat too? This
Autoexec.bat of yours is looking messy/complex. It's calling a ton of
..bat's. Before analyzing them...

Verify you can boot with JUST Config.sys disabled (rename it or uncheck
it at "START button, Run, MSConfig").

If you can boot that way, then probably it is the NOEMS parameter of...
DEVICE=C:\Windows\EMM386.exe NOEMS

....causing the problem. Change it in Config.sys to read...
DEVICE=C:\Windows\EMM386.exe RAM

If that fails, put a REM in front of it...
REM DEVICE=C:\Windows\EMM386.exe NOEMS

If that fails, well, maybe best run without a Config.sys. Or post the
rest of the .bat's...

drivers.bat
initial.bat


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

"Danny" wrote in message
...
| No luck so far!
|
| Here is the spower.bat: @c:\dosboot\pcifind 0x6306 0x1039
| @if errorlevel 1
| c:\windows\system\setpower.exe
|
| Also did not realize I left out a few lines at the end of my
autoexec.bat.
| My apologizies, here it is:
|
| @ECHO OFF
| SET BLASTER=A220 I7 D1 H5 P330 T6
|
| REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT
|
| path C:\WINDOWS;C:\WINDOWS\COMMAND
|
| rem sPower will initialize the USB Keyboard in DOS.
|
| call c:\dosboot\sPower
|
|
| Rem TShoot: if not exist c:\blocks\ml.txt CALL
| c:\windows\temp\Colour\FrstBoot.bat
| rem if not exist c:\blocks\ml.txt CALL
c:\windows\temp\Colour\FrstBoot.bat
| call c:\dosboot\drivers.bat
|
| Rem TShoot: rem - By Windows Setup - mscdex.exe /d:IDECD000 /L:M
| - By Windows Setup - mscdex.exe /d:IDECD000 /L:M
| call c:\hp\specials\initial
|
| Set tvdumpflags=10
|
| SET PATH=%PATH%;C:\PROGRA~1\ATITEC~1\ATICON~1
|
|
|
| Here is what I have tried based on your suggestions:
|
| 1. entered new config.sys. rebooted, VFAT error
|
| 2. removed the dulplicate spower line in autoexec.bat
| put rem in front of other one (rem spower will initialize......)
| rebooted, vfat error
|
| 3. Placed rem in front of the call c:\dosboot\sPower line in
autoexec.bat &
| left rem placed in item 2 above. rebooted, vfat error
|
|
|
|
|
| "PCR" wrote:
|
| | Let us see that "sPower.bat". After it passes muster, try a boot
with
| | the changes above. Then, try with "sPower" deactivated by
unchecking
| it
| | at "START button, Run, MSConfig, Startup tab". However, you must
| double
| | check that it does not turn itself back on!
|
| Autoexec.bat tab, that is.
|
| "PCR" wrote in message
| ...
| ....snip
|
|
|

Yes, I have only been disabling \ bypassing the config.sys. by disabling in
msconfig. It boots with the autoexec.bat enabled.

I did not have the NOEMS parameter in the config.sys until I added with your
recommendations. However I will modify as you suggest and report back.

Yea, since this a remote pc for one of the kids and it is still running
win98se, perhaps being happy that it runs and appears to run well without the
config.sys is not such a bad thing!

"PCR" wrote:

Rereading an earlier post of yours, you said...

"Further troubleshooting has found that the card works and all is well
if I bypass the config.sys during boot."

....Did you mean JUST Config.sys & not Autoexec.bat too? This
Autoexec.bat of yours is looking messy/complex. It's calling a ton of
..bat's. Before analyzing them...

Verify you can boot with JUST Config.sys disabled (rename it or uncheck
it at "START button, Run, MSConfig").

If you can boot that way, then probably it is the NOEMS parameter of...
DEVICE=C:\Windows\EMM386.exe NOEMS

....causing the problem. Change it in Config.sys to read...
DEVICE=C:\Windows\EMM386.exe RAM

If that fails, put a REM in front of it...
REM DEVICE=C:\Windows\EMM386.exe NOEMS

If that fails, well, maybe best run without a Config.sys. Or post the
rest of the .bat's...

drivers.bat
initial.bat


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

"Danny" wrote in message
...
| No luck so far!
|
| Here is the spower.bat: @c:\dosboot\pcifind 0x6306 0x1039
| @if errorlevel 1
| c:\windows\system\setpower.exe
|
| Also did not realize I left out a few lines at the end of my
autoexec.bat.
| My apologizies, here it is:
|
| @ECHO OFF
| SET BLASTER=A220 I7 D1 H5 P330 T6
|
| REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT
|
| path C:\WINDOWS;C:\WINDOWS\COMMAND
|
| rem sPower will initialize the USB Keyboard in DOS.
|
| call c:\dosboot\sPower
|
|
| Rem TShoot: if not exist c:\blocks\ml.txt CALL
| c:\windows\temp\Colour\FrstBoot.bat
| rem if not exist c:\blocks\ml.txt CALL
c:\windows\temp\Colour\FrstBoot.bat
| call c:\dosboot\drivers.bat
|
| Rem TShoot: rem - By Windows Setup - mscdex.exe /d:IDECD000 /L:M
| - By Windows Setup - mscdex.exe /d:IDECD000 /L:M
| call c:\hp\specials\initial
|
| Set tvdumpflags=10
|
| SET PATH=%PATH%;C:\PROGRA~1\ATITEC~1\ATICON~1
|
|
|
| Here is what I have tried based on your suggestions:
|
| 1. entered new config.sys. rebooted, VFAT error
|
| 2. removed the dulplicate spower line in autoexec.bat
| put rem in front of other one (rem spower will initialize......)
| rebooted, vfat error
|
| 3. Placed rem in front of the call c:\dosboot\sPower line in
autoexec.bat &
| left rem placed in item 2 above. rebooted, vfat error
|
|
|
|
|
| "PCR" wrote:
|
| | Let us see that "sPower.bat". After it passes muster, try a boot
with
| | the changes above. Then, try with "sPower" deactivated by
unchecking
| it
| | at "START button, Run, MSConfig, Startup tab". However, you must
| double
| | check that it does not turn itself back on!
|
| Autoexec.bat tab, that is.
|
| "PCR" wrote in message
| ...
| ....snip
|
|
|

Getting better \ interesting!

I tried replacing the NOEMS with RAM. - - - did not resolve issue.

However, since there are only 5 lines in the new config.sys, I decided to
rem them one at a time. Here is what I found:

Rem 'ing both of these lines, individually allowed a boot with no issues
DEVICE=C:\Windows\HIMEM.sys
DEVICE=C:\Windows\EMM.386.exe NOEMS

When the HIMEM.sys was rem'ed, I got an error during startup stating that
EMM386 not installed - xms mgr not present

When the EMM.386 line was rem'ed, no messages.

I checked and the EMM386.exe file is present under the windows directory.


Looks like it is now narrowed down, but i have no clue!!



"Danny" wrote:

Yes, I have only been disabling \ bypassing the config.sys. by disabling in
msconfig. It boots with the autoexec.bat enabled.

I did not have the NOEMS parameter in the config.sys until I added with your
recommendations. However I will modify as you suggest and report back.

Yea, since this a remote pc for one of the kids and it is still running
win98se, perhaps being happy that it runs and appears to run well without the
config.sys is not such a bad thing!

"PCR" wrote:

Rereading an earlier post of yours, you said...

"Further troubleshooting has found that the card works and all is well
if I bypass the config.sys during boot."

....Did you mean JUST Config.sys & not Autoexec.bat too? This
Autoexec.bat of yours is looking messy/complex. It's calling a ton of
..bat's. Before analyzing them...

Verify you can boot with JUST Config.sys disabled (rename it or uncheck
it at "START button, Run, MSConfig").

If you can boot that way, then probably it is the NOEMS parameter of...
DEVICE=C:\Windows\EMM386.exe NOEMS

....causing the problem. Change it in Config.sys to read...
DEVICE=C:\Windows\EMM386.exe RAM

If that fails, put a REM in front of it...
REM DEVICE=C:\Windows\EMM386.exe NOEMS

If that fails, well, maybe best run without a Config.sys. Or post the
rest of the .bat's...

drivers.bat
initial.bat


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

"Danny" wrote in message
...
| No luck so far!
|
| Here is the spower.bat: @c:\dosboot\pcifind 0x6306 0x1039
| @if errorlevel 1
| c:\windows\system\setpower.exe
|
| Also did not realize I left out a few lines at the end of my
autoexec.bat.
| My apologizies, here it is:
|
| @ECHO OFF
| SET BLASTER=A220 I7 D1 H5 P330 T6
|
| REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT
|
| path C:\WINDOWS;C:\WINDOWS\COMMAND
|
| rem sPower will initialize the USB Keyboard in DOS.
|
| call c:\dosboot\sPower
|
|
| Rem TShoot: if not exist c:\blocks\ml.txt CALL
| c:\windows\temp\Colour\FrstBoot.bat
| rem if not exist c:\blocks\ml.txt CALL
c:\windows\temp\Colour\FrstBoot.bat
| call c:\dosboot\drivers.bat
|
| Rem TShoot: rem - By Windows Setup - mscdex.exe /d:IDECD000 /L:M
| - By Windows Setup - mscdex.exe /d:IDECD000 /L:M
| call c:\hp\specials\initial
|
| Set tvdumpflags=10
|
| SET PATH=%PATH%;C:\PROGRA~1\ATITEC~1\ATICON~1
|
|
|
| Here is what I have tried based on your suggestions:
|
| 1. entered new config.sys. rebooted, VFAT error
|
| 2. removed the dulplicate spower line in autoexec.bat
| put rem in front of other one (rem spower will initialize......)
| rebooted, vfat error
|
| 3. Placed rem in front of the call c:\dosboot\sPower line in
autoexec.bat &
| left rem placed in item 2 above. rebooted, vfat error
|
|
|
|
|
| "PCR" wrote:
|
| | Let us see that "sPower.bat". After it passes muster, try a boot
with
| | the changes above. Then, try with "sPower" deactivated by
unchecking
| it
| | at "START button, Run, MSConfig, Startup tab". However, you must
| double
| | check that it does not turn itself back on!
|
| Autoexec.bat tab, that is.
|
| "PCR" wrote in message
| ...
| ....snip
|
|
|

Yes you did have the NOEMS parameter in Config.sys, per your earlier
post of the file...

.......Quote..............
| [common]
| dos=high,umb
| buffers=40
| device=c:\windows\himem.sys /testmemff
| DEVICE=C:\WINDOWS\EMM386.EXE NOEMS
| REM DEVICE=C:\WINDOWS\EMM386.EXE NOEMS
|
| rem The below DOS CD ROM driver is not required to run Windows 98.
| rem DEVICE=c:\cdrom\OakCdRom.SYS /D:IDECD000
.......EOQ................

It's really cquirke's &/or Blanton's job to explain these things, BUT...

NOEMS tells EMM386.exe to disallow Expanded Memory, which could be used
for "loading 16-bit drivers, TSRs, & portions of DOS" (by my book,
Windows 98 Secrets [Livingston/Straub]). Changing NOEMS to RAM will
allow it, but not to full capacity, 64K subtracted. This apparently was
not good enough for that mess in Autoexec.bat to abide. Putting a REM in
front does cure you. Therefore, by all means, run it that way.

| When the HIMEM.sys was rem'ed, I got an error during startup stating
that
| EMM386 not installed - xms mgr not present

Right. If there is an EMM386.exe line, a HIMEM.sys must precede it!

Well, now that you can boot, well, still may as well get an analysis of
all those .bat files. It may not be me who provides the best analysis of
it, though. Post something containing all of them in this order...

Config.sys
Autoexec.bat
sPower.bat
FrstBoot.bat
drivers.bat
initial.bat


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

"Danny" wrote in message
...
| Getting better \ interesting!
|
| I tried replacing the NOEMS with RAM. - - - did not resolve issue.
|
| However, since there are only 5 lines in the new config.sys, I decided
to
| rem them one at a time. Here is what I found:
|
| Rem 'ing both of these lines, individually allowed a boot with no
issues
| DEVICE=C:\Windows\HIMEM.sys
| DEVICE=C:\Windows\EMM.386.exe NOEMS
|
| When the HIMEM.sys was rem'ed, I got an error during startup stating
that
| EMM386 not installed - xms mgr not present
|
| When the EMM.386 line was rem'ed, no messages.
|
| I checked and the EMM386.exe file is present under the windows
directory.
|
|
| Looks like it is now narrowed down, but i have no clue!!
|
|
|
| "Danny" wrote:
|
| Yes, I have only been disabling \ bypassing the config.sys. by
disabling in
| msconfig. It boots with the autoexec.bat enabled.
|
| I did not have the NOEMS parameter in the config.sys until I added
with your
| recommendations. However I will modify as you suggest and report
back.
|
| Yea, since this a remote pc for one of the kids and it is still
running
| win98se, perhaps being happy that it runs and appears to run well
without the
| config.sys is not such a bad thing!
|
| "PCR" wrote:
|
| Rereading an earlier post of yours, you said...
|
| "Further troubleshooting has found that the card works and all is
well
| if I bypass the config.sys during boot."
|
| ....Did you mean JUST Config.sys & not Autoexec.bat too? This
| Autoexec.bat of yours is looking messy/complex. It's calling a ton
of
| ..bat's. Before analyzing them...
|
| Verify you can boot with JUST Config.sys disabled (rename it or
uncheck
| it at "START button, Run, MSConfig").
|
| If you can boot that way, then probably it is the NOEMS parameter
of...
| DEVICE=C:\Windows\EMM386.exe NOEMS
|
| ....causing the problem. Change it in Config.sys to read...
| DEVICE=C:\Windows\EMM386.exe RAM
|
| If that fails, put a REM in front of it...
| REM DEVICE=C:\Windows\EMM386.exe NOEMS
|
| If that fails, well, maybe best run without a Config.sys. Or post
the
| rest of the .bat's...
|
| drivers.bat
| initial.bat
|
|
| --
| Thanks or Good Luck,
| There may be humor in this post, and,
| Naturally, you will not sue,
| should things get worse after this,
| PCR
|
| "Danny" wrote in message
| ...
| | No luck so far!
| |
| | Here is the spower.bat: @c:\dosboot\pcifind 0x6306 0x1039
| | @if errorlevel 1
| | c:\windows\system\setpower.exe
| |
| | Also did not realize I left out a few lines at the end of my
| autoexec.bat.
| | My apologizies, here it is:
| |
| | @ECHO OFF
| | SET BLASTER=A220 I7 D1 H5 P330 T6
| |
| | REM To make a DOS Boot Diskette; See the file
C:\DOSBOOT\DOSBOOT.TXT
| |
| | path C:\WINDOWS;C:\WINDOWS\COMMAND
| |
| | rem sPower will initialize the USB Keyboard in DOS.
| |
| | call c:\dosboot\sPower
| |
| |
| | Rem TShoot: if not exist c:\blocks\ml.txt CALL
| | c:\windows\temp\Colour\FrstBoot.bat
| | rem if not exist c:\blocks\ml.txt CALL
| c:\windows\temp\Colour\FrstBoot.bat
| | call c:\dosboot\drivers.bat
| |
| | Rem TShoot: rem - By Windows Setup - mscdex.exe /d:IDECD000 /L:M
| | - By Windows Setup - mscdex.exe /d:IDECD000 /L:M
| | call c:\hp\specials\initial
| |
| | Set tvdumpflags=10
| |
| | SET PATH=%PATH%;C:\PROGRA~1\ATITEC~1\ATICON~1
| |
| |
| |
| | Here is what I have tried based on your suggestions:
| |
| | 1. entered new config.sys. rebooted, VFAT error
| |
| | 2. removed the dulplicate spower line in autoexec.bat
| | put rem in front of other one (rem spower will
initialize......)
| | rebooted, vfat error
| |
| | 3. Placed rem in front of the call c:\dosboot\sPower line in
| autoexec.bat &
| | left rem placed in item 2 above. rebooted, vfat error
| |
| |
| |
| |
| |
| | "PCR" wrote:
| |
| | | Let us see that "sPower.bat". After it passes muster, try a
boot
| with
| | | the changes above. Then, try with "sPower" deactivated by
| unchecking
| | it
| | | at "START button, Run, MSConfig, Startup tab". However, you
must
| | double
| | | check that it does not turn itself back on!
| |
| | Autoexec.bat tab, that is.
| |
| | "PCR" wrote in message
| | ...
| | ....snip
| |
| |
| |
|
|
|

On Sat, 13 Aug 2005 19:15:02 -0700, "Danny"

When the EMM.386 line was rem'ed, no messages.

This is a fairly common failure pattern, and indicates a contention
within the UMB area. Patience; soon you'll know what I mean!

At the rawest level, a computer starts with programs running in ROM
(read-only memory chips) and working in RAM. In the case of the PC,
there are at least two ROMs; one for the system BIOS, and one for the
graphics card. Additional ROMs for LAN card, SCSI etc. are possible.

IBM took the crazy decision to locate these ROMs not from address 0,
so that RAM could expand upwards as far as the hardware could address,
but at address 640k, going up to the "end of the world" at 1M.

This region of the memory map is called Upper Memory Blocks, and all
sorts of things stomp around here as if they owned the place - system
BIOS, original VGA BIOS, enlargements of both of these, "scratch"
workspace for these and other entities, the EMS frame, etc.

Normally, DOS and Win9x doesn't try to use this space at all. EMS
hardware's pretty much extinct now, but EMM386.exe was added around
MS-DOS 5 or so, to emulate EMS for programs that expected it. In
addition, if DOS=UMB, Emm386.exe can also make puddles of free RAM
(between all the ROMs) available for DOS use. And so the pain begins.

What goes wrong, is that Emm386.exe may think an area of UMB is not
used, when it is. When two processes try to use the same RAM, bad
things happen, as one might expect!

Emm386.exe has syntax that allows one to force it to ignore (eXclude)
areas of UMB that it might have thought free otherwise. So you could
experiment with exclusion parameters, to find the smallest area you
can exclude that will aviod the problem.

But if you don't need EMS or UMB access, it's easier to simply remove
the reference to Emm386.exe altogether. If you do need EMS, but not
UMB, then drop the DOS=UMB line instead; that may be enough, or you
may have to explicitly set the page frame address via the appropriate
parameter, if the default page fram location crashes into whatever's
lurking there (my guess would be SVGA workspace).




------------ ----- ---- --- -- - - - -
The most accurate diagnostic instrument
in medicine is the Retrospectoscope
------------ ----- ---- --- -- - - - -

He has half a ton of .bat's called in his Autoexec.bat, cquirke.
Apparently they don't like EMM386.exe at all-- whether NOEMS or RAM is
used on it! I have asked that he put them all into one post. Please
don't let me be the one to analyze them!


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

"cquirke (MVP Windows shell/user)" wrote
in message ...
| On Sat, 13 Aug 2005 19:15:02 -0700, "Danny"
|
| When the EMM.386 line was rem'ed, no messages.
|
| This is a fairly common failure pattern, and indicates a contention
| within the UMB area. Patience; soon you'll know what I mean!
|
| At the rawest level, a computer starts with programs running in ROM
| (read-only memory chips) and working in RAM. In the case of the PC,
| there are at least two ROMs; one for the system BIOS, and one for the
| graphics card. Additional ROMs for LAN card, SCSI etc. are possible.
|
| IBM took the crazy decision to locate these ROMs not from address 0,
| so that RAM could expand upwards as far as the hardware could address,
| but at address 640k, going up to the "end of the world" at 1M.
|
| This region of the memory map is called Upper Memory Blocks, and all
| sorts of things stomp around here as if they owned the place - system
| BIOS, original VGA BIOS, enlargements of both of these, "scratch"
| workspace for these and other entities, the EMS frame, etc.
|
| Normally, DOS and Win9x doesn't try to use this space at all. EMS
| hardware's pretty much extinct now, but EMM386.exe was added around
| MS-DOS 5 or so, to emulate EMS for programs that expected it. In
| addition, if DOS=UMB, Emm386.exe can also make puddles of free RAM
| (between all the ROMs) available for DOS use. And so the pain begins.
|
| What goes wrong, is that Emm386.exe may think an area of UMB is not
| used, when it is. When two processes try to use the same RAM, bad
| things happen, as one might expect!
|
| Emm386.exe has syntax that allows one to force it to ignore (eXclude)
| areas of UMB that it might have thought free otherwise. So you could
| experiment with exclusion parameters, to find the smallest area you
| can exclude that will aviod the problem.
|
| But if you don't need EMS or UMB access, it's easier to simply remove
| the reference to Emm386.exe altogether. If you do need EMS, but not
| UMB, then drop the DOS=UMB line instead; that may be enough, or you
| may have to explicitly set the page frame address via the appropriate
| parameter, if the default page fram location crashes into whatever's
| lurking there (my guess would be SVGA workspace).
|
|
|
|
| ------------ ----- ---- --- -- - - - -
| The most accurate diagnostic instrument
| in medicine is the Retrospectoscope
| ------------ ----- ---- --- -- - - - -

On Sun, 14 Aug 2005 13:56:55 -0400, "PCR" wrote:

He has half a ton of .bat's called in his Autoexec.bat, cquirke.
Apparently they don't like EMM386.exe at all-- whether NOEMS or RAM is
used on it! I have asked that he put them all into one post. Please
don't let me be the one to analyze them!

Easiest is to press Shift+F8 and single-step through the .bat (this
will single-step what is Called as well as Autoexec.bat itself) to see
where it dies. Then it's either the Emm386.exe shenanigans I
detailed, or that particular part of that .bat gets the bullet :-)

On Emm386.exe syntax:

Emm386.exe RAM
- emulates EMS
- provides UMB services, if facilitated by DOS=UMB

Emm386.exe NoEMS
- provides UMB services only, if facilitated by DOS=UMB

IOW, both will do UMB if facilitated no DOS=UMB (which is the default
in Win9x unless suppressed via DOS=NoAuto)

The "RAM" parameter will be less effective as there will be the 64k
lump taken up by the EMS page frame - but both "do" UMB.



------------------------ ---- --- -- - - - -
Forget http://cquirke.blogspot.com and check out a
better one at http://topicdrift.blogspot.com instead!
------------------------ ---- --- -- - - - -

"cquirke (MVP Windows shell/user)" wrote
in message ...
| On Sun, 14 Aug 2005 13:56:55 -0400, "PCR" wrote:
|
| He has half a ton of .bat's called in his Autoexec.bat, cquirke.
| Apparently they don't like EMM386.exe at all-- whether NOEMS or RAM
is
| used on it! I have asked that he put them all into one post. Please
| don't let me be the one to analyze them!
|
| Easiest is to press Shift+F8 and single-step through the .bat (this
| will single-step what is Called as well as Autoexec.bat itself) to see
| where it dies. Then it's either the Emm386.exe shenanigans I
| detailed, or that particular part of that .bat gets the bullet :-)

IT IS the Emm386.exe shenanigans, cquirke, as he can boot well with
Autoexec.bat enabled-- just not with Config.sys.

STILL, it wouldn't hurt to have a look at his .bat's. If all of it is
meant only to activate things in DOS, perhaps some of it can be moved to
DOSStart.bat.

|
| On Emm386.exe syntax:
|
| Emm386.exe RAM
| - emulates EMS
| - provides UMB services, if facilitated by DOS=UMB
|
| Emm386.exe NoEMS
| - provides UMB services only, if facilitated by DOS=UMB
|
| IOW, both will do UMB if facilitated no DOS=UMB (which is the default
| in Win9x unless suppressed via DOS=NoAuto)
|
| The "RAM" parameter will be less effective as there will be the 64k
| lump taken up by the EMS page frame - but both "do" UMB.

That is also my understanding of it, book-learning only, though, if even
that. I DID find myself running to prior posts & back to the book itself
on this one. And I'll probably go running back next time too. Also,
putting one of your current posts into my "Keepers", I notice I had nine
there already that mentioned EMM386, not to mention one each by Bill
Watt, Terhune, John Payne, & Phydeaux. Lord, what a mind twister it is!
You do make it sound nearly understandable, though.

|
|
|
| ------------------------ ---- --- -- - - - -
| Forget http://cquirke.blogspot.com and check out a
| better one at http://topicdrift.blogspot.com instead!
| ------------------------ ---- --- -- - - - -