#qemm after 3ds4 load?
15 messages in this thread
Howdy Yosters, ALL
I've been setting up a pentium 66MHz Eisa system with 32MB Ram and 1.8 gig
drive for programs and a 2.1 Gig Barracuda for the MAtrox Max Setup.
I've loaded the 3ds4, Matrox's Max software Plus Workgroup for Windows 3.11.
When I try to load QEMM's manager I'm able to recover more memory but 3DS4
refuses to work. I get an error message about not being able to initialize the
RDPADI Driver for the Illuminator Pro board but that usually only happens when
you've forgotten to put the CALLB 2 line in PHarLap.
Does the fact that I've loaded 3ds4 first and let pharlap look at the system
before I have QEMM loaded cause this problem.
If so What should I do to correct it?
Thanks in advance,
Murph'
Lucky for you I had this same problem this past week-and fixed it<g>. You have
to run the config.bat(or something like that) that ships with the Matrox to
modify the PharLap settings after you install 3DS. This allows that Illuminator
Pro to work correctly in 386 Protected Mode. The file is located on the disks
that ship with the MAX setup.
Jh
Jeremy,
I'm not sure you understand what I'm saying.
I loaded 3ds4 and all the matrox stuff it all works fine.
Then I loaded QEMM and couldn't fire up 3ds4 because I was getting an error
that said RDPADI wasn't being initialized.
I assume that's a Phar Lap error then and that by rerunning the max config
program it's fix it????
I'm not sure if that's right.
Could you explain this in more detail?
thank you.
Murph'
I'm just saying to re-run that matrox batch file that modifies the Phar Lap
settings. It should make the necessary corrections. But, if you're saying that
after you loaded QEMM, the problems starting-I'm kinda baffled.
Jh
Jeremy,
>>> I'm just saying to re-run that matrox batch file that modifies the Phar Lap
settings <<<
Since I run all the files in logical order when installing and I've allready
delivered the systems without the benefit of QEMM, I'd have to wait until I get
another system in to work with it.
I don't remember which batch file that actually was right now.
The systems work fine without it, I'm just hoping that if I free up even more
memory with QEMM they might work even faster.
Right now they are rock solid with MS-DOS's utilities.
However I'm always trying to improve things.
Thanks for the response, I'll be getting another system in soon hopefully I'll
be able to keep it a little longer before someone falls in love with it and
demands I sell them my "working system".
I've gone through two systems like this.
Acutally It's pretty good because I'm always able to upgrade to the best
motherboards this way.
Right now the Pentium 66MHz's units are running great….Once you learn all
those special little tricks…He…He….:-)
Murph'
<<However I'm always trying to improve things.>>
Ah…you've got the fever too!
Jh
Jeremy,
Not so much a fever as an obsesive compulsive need to be the best! <G>
Murph'
James,
Thanks for getting the upgrade to me so quickly, I had a problem running the
vibcfg file, but its working now.
What I wanted to ask you is just how much better is Qemm 7.5 than 6.0, is it
worth upgrading?
Regards……..Rick – Technical Animations
>> is just how much better is Qemm 7.5 than 6.0, is it worth upgrading?
PMJI, but a very emphatic YES! I was on QEMM 6.x, skipped 7.0
totally, and just got 7.5 myself. I was extremely pleased to see
that Optimize _properly_ recognized everything in my computers and
gave me more memory, also! I used to dread upgrading the memory
manager, but this was definitely worth it!
PMFJB, That great to here, from there hype I couldn't tell what it
would do for me, thanks again.
PMFJB = Pardon Me For Jumping Back<BG>.
BTW, I'm planning on upload the "Forensic Animator List" by next
tuesday.
PMFJBKMYSF = Pardon Me For Jumping Back, Kiss Myself, Eaaayah, So Fine.
John,
>>PMFJBKMYSF = Pardon Me For Jumping Back, Kiss Myself, Eaaayah, So Fine.<<
What ever floats your skirt …….. I heard you had one <BG>.
Regards…………Rick – Technical Animations
Optimize 7.01-ish didn't recognize everything in my computer, which made QEMM
reorganization very frustrating. My CONFIG.SYS starts out:
DEVICE=C:\QEMM\DOSDATA.SYS
REM Fix Exception 13 problems with UltraStors
DEVICE=C:\QEMM\ULTRAFIX.SYS
REM UltraStor ASPI, between DOSDATA and QEMM, don't scan x300 Ethernet
DEVICE=USPI14.SYS /F /X300
DEVICE=C:\QEMM\QEMM386.SYS RAM XST=C000 R:2
Rick, I beleive Greg has the answer for ya' <g>. I need to spend
some time going over my Card addresses etc as I've switched SCSI
Controllers, Sound Cards and Video cards but I'm still getting away
with the old Addresses. Me-Thinks I got a little house cleaning to
do because I just tried to load Video Clipboard and it's locking
things up…that points to a conflict someplace even though
everything else works. Some programs are more tolerant than others
as well as the possibility that I may even be shareing an IRQ with
somethin' No Matter I'm ready to strip out everything and start over
anyway cause I gotta find a better VLB Graphics card for this machine
because I want to run TrueColor at 16Million for the Mirage routine
stuff. It never ends! 🙂 Have a happy Turkey day! Murph'