Clearly the easy win is to dump Dblspace and Stacker
On 2/25/19 1:55 PM, Kerr-Mudd,John wrote:
Clearly the easy win is to dump Dblspace and Stacker
Would DoubleSpace / Stacker / DriveSpace mount an image that comes from
a network drive?
Not that I would want to.
I'm just wondering if it would work.
Here's the memory layout of the Win98 PC during network mode as promised: --------------------------[snip]
Isolate the problem. Use switches to disable QEMM features in order to use >> minimum features. If everything is already disabled but still froze/crash >> the system, it means that QEMM is not compatible with the computer (which >> usually, the motherboard chipset). If it loads OK, remove the switches one >> by one to enable one feature at a time, so that you'll know which feature isRemoving the RA parameter helped, but I *need* UMBs. :(
causing the problem.
Which program loads ASPIPPM1, DOSNET, and SERIAL? I don't see them being loaded in AUTOEXEC.BAT. And what is their actual execution order?
You're already using Stacker. Don't load DoubleSpace. Use DoubleSpace only
if you're having problem with Stacker.
Of course you need the UMB. What you need to disable is everything except
UMB support or its required features. QEMM is an optimistic memory manager. Its changes to crash the system is pretty high. Especially for hardwares which are released after that QEMM version is released.
I'm aware of no program to share Win98 drives with a DOS computer.
Okay. I'm at my mother's house right now and can try to disable DriveSpace DOS. The proper lines in the MSDOS.SYS file are DblSpace=0 and DrvSpace=0, right?
On Saturday, March 2, 2019 at 10:12:03 AM UTC-5, Harry Potter wrote:
Okay. I'm at my mother's house right now and can try to disable DriveSpace DOS. The proper lines in the MSDOS.SYS file are DblSpace=0 and DrvSpace=0, right?
I did, and now, I have 437k free conventional memory. :) What more can I do?
Use 32 bit Watcom compiler.
I have an astro program with 400.000 stars and galaxys in t.
Using about 45 megabyte memory.
I'm *still* looking for more RAM from my Win98 computer's network DOS configuration. At the very least, I want to get QEMM's VidRAM utility
to give me only 64k as my config. uses the mono video buffer for UMBs.
DOS networking and Win98 don't mix well. It's a recipe for frustation.
Many older network cards have a Win98 driver. What network card do you
have?
I didn't think there was any problem running DOS networking on MS-DOS
7.x ('98 MS-DOS mode).
Which is what I think the OP is doing.
But why suffer QEMM?
But why suffer QEMM?
I think that some of an answer to your question is in the rest of this thread.
BTW, I'm using a .PIF file in DOS mode for the config.
You have a lot of stuff in your config. The first thing I do is get rid
of everything and start over, adding one piece at a time until I see
where the problem is.
I don't use stacker, I can't help you with that. Can you get rid of it
for testing?
I see dosnet, network, and network\rar in your path. Please explain each piece and its intended use. Without the big picture, I can't help much.
BTW, I'm using a .PIF file in DOS mode for the config.
A .PIF file in DOS mode? I'm not sure what that means. Are you booting
into DOS using a shortcut from the Windows GUI? Not that it matters, but
I never do that. I either boot to DOS command line or boot the Windows
GUI, using MDSOS.SYS file directives:
WinDir=D:\WINDOWS--- Synchronet 3.17c-Linux NewsLink 1.110
WinBootDir=D:\WINDOWS
HostWinBootDrv=D
[Options]
BootMulti=1
BootGUI=1
DoubleBuffer=0
AutoScan=1
WinVer=4.10.2222
BootMenu=1
BootMenuDelay=5
; BootMenuDefault=5
Logo=0
DisableLog=1
SystemReg=0
DblSpace=0
DrvSpace=0
Network=0
;
The problem is low Conventional memory.
stacker ... Can you get rid of it for testing?I can get rid of it for testing, but it is needed for the network.
dosnet is the network software; IIRC network is the stuff used by the network, and network\rar is the DOSRAR archiver.
A .PIF file in DOS mode? I'm not sure what that means. Are you booting
into DOS using a shortcut from the Windows GUI?
Yes, I did. I do this because the network I'm using requires an extra setup.
Stacker is disk compresssion. What that has to do with a network, is a mystery to me.
dosnet is the network software; IIRC network is the stuff used by the network, and network\rar is the DOSRAR archiver.
Your replies are cryptic. Please explain what you want.
A .PIF file in DOS mode? I'm not sure what that means. Are you booting
into DOS using a shortcut from the Windows GUI?
Yes, I did. I do this because the network I'm using requires an extra setup.
An extra setup? You mean it won't work unless you boot the GUI first?
That's messed up.
I can't spend much time untangling this mess, I have my own messes to untangle. I can give you ideas on how to proceed, but you have to get
dirty and do the work.
Tell me the big picture, what you want to do.
One of the networked drives is compressed using Stacker.
An extra setup? You mean it won't work unless you boot the GUI first?
That's messed up.
Actually, yes, but I could use a floppy to start the system.
I just want to buy myself some more Conventional RAM.
At least 500k if possible.
BTW, is there a utility to increase the Conventional RAM by 64k
if the mono graphics buffer is used as UMBs?
I just want to buy myself some more Conventional RAM.
At least 500k if possible.
Should not be a problem with himem and emm386.
BTW, is there a utility to increase the Conventional RAM by 64k
if the mono graphics buffer is used as UMBs?
32k with emm386 and a i=b000-b7ff parameter. But if your video card is
VGA or higher, don't do it, it's unstable.
I'm not sure you're serious, but if you are, explain your network requirements in detail. Otherwise, I'm losing interest.Basically, the network treats a Stacker-compressed Zip100 disk and a RAM-drive as extra simulated hard drives for a DOS laptop with no hard drive along with a local Zip100 disk and RAM drive. I'm doing this to add more usable drive space to the DOS laptop. The DOS laptop works fine with QEMM, but QEMM doesn't work properly on my Win98 computer. That's why I'm asking.
I do thatBTW, is there a utility to increase the Conventional RAM by 64k
if the mono graphics buffer is used as UMBs?
32k with emm386 and a i=b000-b7ff parameter. But if your video card is
VGA or higher, don't do it, it's unstable.
but I want to map A000-AFFF to Conventional memory if possible.
explain your network requirements in detail
Basically, the network
treats a Stacker-compressed Zip100 disk and a
RAM-drive as extra simulated hard drives for a DOS laptop with no hard
drive along with a local Zip100 disk and RAM drive. I'm doing this to
add more usable drive space to the DOS laptop. The DOS laptop works
fine with QEMM, but QEMM doesn't work properly on my Win98 computer.
That's why I'm asking
One of the networked drives is compressed using Stacker.
Basically, the network treats a Stacker-compressed Zip100 disk and a RAM-drive as extra simulated hard drives for a DOS laptop with no hard
drive along with a local Zip100 disk and RAM drive. I'm doing this to
add more usable drive space to the DOS laptop. The DOS laptop works
fine with QEMM, but QEMM doesn't work properly on my Win98 computer.
That's why I'm asking.
On 3/24/19 1:02 PM, Harry Potter wrote:
One of the networked drives is compressed using Stacker.
So do you use Stacker to mount a compressed drive image and then load
the network driver from there?
On 3/24/19 1:46 PM, Harry Potter wrote:
Basically, the network treats a Stacker-compressed Zip100 disk and a
RAM-drive as extra simulated hard drives for a DOS laptop with no hard
drive along with a local Zip100 disk and RAM drive
Elsewhere in this thread you indicated that you were networking across
the serial port and not Ethernet
I'm sorry for not being clear. I'm using NetSoft LAN with a null-modem serial connection.
I'm booting the laptop from a floppy. The laptop doesn't have a CD-ROM drive, but I plan on sharing the Win98 computer's USB CD-ROM drive.
To do that, I need more RAM on the Win98 PC. I'm using the mono video buffer for UMBs because I don't use that RAM for video: my first PC did that. … Does this help?
Please back up and refresh me / us on what is running on what machines,
what mode they are running in, and why.
Compressed network drives on a serial port lan? I know when to quit and
move on.
On 3/24/19 4:03 PM, Harry Potter wrote:
I'm booting the laptop from a floppy. The laptop doesn't have a CD-ROM drive, but I plan on sharing the Win98 computer's USB CD-ROM drive.
How well does (what I'm going to call) DOS'98 like the USB CD-ROM? Is
there a reason that you're using USB instead of IDE / SCSI in the machine?
I say this because I think you're going to need another driver to get
DOS'98 to see the USB CD-ROM. Yet something else fighting you for memory.
To do that, I need more RAM on the Win98 PC. I'm using the mono video buffer for UMBs because I don't use that RAM for video: my first PC did that. … Does this help?
Yes, it does help.
I don't recall, why are you booting the '98 machine into MS-DOS mode?
So that you can run the NetSoft LAN?
I ask because I'm wondering if there's a chance that INTERLNK & INTERSVR might be made to work inside of Windows. I want to say that I had
INTERSVR working in a MS-DOS window on my '98 machine back in the day.
But it's been too long for me to say with any degree of certainty.
Are you using serial instead of parallel because of the parallel port
Zip drives?
Do you /need/ the Zip drive on the DOS laptop? Or could it be moved to
the '98 machine and shared with the DOS laptop via network? - Or am I conflating where your memory problem is again?
This thread's been on going for a month. So it's not like it is
anything fast or time demanding.
I don't know yet, as I didn't try it. I want more memory first.
Pretty much so.
Yes.
I did at first, but I prefer NSLAN, as I get to share specific folders,
not just drives.
Yes.
The local Zip drive acts as a simulated hard drive before the network
is in place. The network loads from there.
Have you tried the parallel cable between the two Zip drives? Does it
work? Does it error out? What happens?
Do you mean anything special by "simulated hard drive"? Because to me,
it's just another drive letter. One that happens to be on something
other than an internal hard drive.
I need the Zip drive attached to the Win98 PC for other purposes as well,
so I can't attach it directly to the other Zip drive. :(
When I say by "simulated hard drive" I mean something to take the place
of a real hard drive wher none exists.
I am looking for a way to use the memory at $A000-$AFFF
I am looking for a way to use the memory at $A000-$AFFF but not
$B000-$B7FF as extra Conventional memory. What program can do that?
Where can I find it on-line?
I am looking for a way to use the memory at $A000-$AFFF but not
$B000-$B7FF as extra Conventional memory. What program can do that?
Where can I find it on-line?
emm386.exe. But you'll have to run all your programs in B&W monochrome
text. (so no w98)
QEMM comes with a utility called VidRAM that temporarily allows the use
of the VGA video buffer as Conventional memory. That is what I want: *temporary* use of the RAM at $A000-$AFFF as Conventional memory.
The Win98 computer can run a .PIF file that sets up a temporary
network with a DOS/Win16 laptop.
T. Ment, can you repeat the help, please? I can't find it.
VidRAM may work with CGA video cards, but they are rare now. I doubt you
have one. It's unstable with VGA.
The Win98 computer can run a .PIF file that sets up a temporary
network with a DOS/Win16 laptop.
You don't need a Win98 PIF file. I setup a Netsoft serial port LAN
between two computers, and I did not need Win98. My low DOS memory was
600K+. Your setup is too complicated. Simplify it.
T. Ment, can you repeat the help, please? I can't find it.
Strip everything out of your config and boot to bare DOS, See how much
memory you have. Reinstall Netsoft LAN with minimum options. See again
how much memory you have. Add things back into your config, one at a
time, until you see which one is the memory hog.
It's a step by step process anyone can do. But you seem unwilling to do
the work.
I *could* use a start-up floppy to start the network. I use a PIF
file because the network is temporary, and, when I'm done with the
network, I want to reboot to Win98.
The reason I am unwilling to do the work is because I want *all* the
programs to be loaded at start-up.
BTW, the files listed in my second post here are for the Win98 DOS mode network configuration.
I just looked at my config. files as posted here and can only
remove DOSKEY and the CD driver, but DOSKEY is very small and
the CD driver may be needed soon.
You don't listen do you. You must be female. All talk no listen. I don't
give much time to nagging females.
Not cool.
Please hold the insults and keep it friendly.
You don't listen do you. You must be female. All talk no listen. I don't
give much time to nagging females.
I'm *not* a female.
I don't understand what I'm doing wrong.
Again, I don't know what I can remove from the setup
I need most of the items in the setup.
… use MSDOS.SYS to configure the Win98 boot menu … instead of using
a PIF file to boot into DOS from Win98. That simplifies things, so that Win98 is not involved in your low memory problem.
Stop thinking about what you want, and start working to diagnose the
memory hog. Temporarily, remove everything. Make copies of your startup files to keep backups of them, then strip everything out of the working copies and start from scratch.
And I have no interest in that.
I agree that booting into Windows and then rebooting into MS-DOS mode is >largely unnecessary for the OP's stated goal. But I don't see how that >sequence alters what is (not) loaded in the MS-DOS mode's configuration.
And I have no interest in that.
So ignore it.
You can't be sure Win98 has no effect on DOS memory rebooted from a PIF.
To make sure, don't do that. Use the Win98 boot menu to go straight into
DOS after power up.
The book DOS Internals discusses problems of warm rebooting.
And I have no interest in that.
So ignore it.
If you don't like them, you can ignore my posts too.
Windows doesn't boot up in the custom config. as the .PIF file
containing the config. boots in DOS mode.
I found the memory hog: DriveSpace boots with the system. I disabled it and now have 517k Conventional memory. :D I want to load the ASPIPPM1 driver high but had no success. :( I'll try again.
Try using SlimWin, it makes windows from 1GB to 46MB.
On Sunday, April 14, 2019 at 11:21:26 AM UTC-4, olliet...@gmail.com wrote:
Try using SlimWin, it makes windows from 1GB to 46MB.
How will that help?
Uhh...I still have the memory hole,
and Windows keeps resetting MSDOS.SYS
and its D*Space entries when I exit
the network mode. :(
I added to the EMM386 command line the NOEMS parameter, and it bought
me a lot of memory. :)
64k I'd imagine.
Yes, but using EMM386 without EMS is problematic
It'd be better to use >plain UMB manager
What problem?
You mean UMBPCI? It's not always compatible with ISA DMA in UMBs.
Depends on the chipset. EMM386 does not have the problem.
Some protected mode programs will fail to run. As if the VM86 mode that EMM386 have set up, got crippled.
You mean UMBPCI? It's not always compatible with ISA DMA in UMBs.
Depends on the chipset. EMM386 does not have the problem.
Yes. I'm aware that it's not for all systems. I mean, if it's applicable, it's better to use it than EMM386 if UMB is the priority. EMM386 is more successful on providing UMB, but it uses VM86 mode for that.
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 997 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 224:54:10 |
| Calls: | 13,046 |
| Calls today: | 1 |
| Files: | 186,574 |
| Messages: | 3,292,757 |