#AniPro 1.3 vs. QEMM 7.1
23 messages in this thread
Help! Does anyone know why Animator Pro 1.3 consistently — ALWAYS
— bombs under QEMM 7.1 (with ST:M)? It will not run on any of our
QEMM 7.1 equipped machines unless I reboot without QEMM! It usually
locks up the machine completely (even beyond the reach of
[Ctrl]+[Alt]+[Del]!) before it ever appears on the screen. Is there
a fix available?
Marion,
First QEMM386 is not 7.02 as the 7.01 was a little flakey. You can
either upgrade your copies or download a patch from the QuarterDesk
forum. Then, is your graphics card (or cards) Tesng 4000 based ???
If so there is a little conflict between the memory manager and the
chip. The easiest solution is to *NOT* load DOS HIGH. (this has been
discovered by several people the hard way…..<g>)
I've got 7.02, and don't use an ET4000 chipset. I have yet to be able
to change screen sizes without getting kicked out to BIG DOS LETTERS
reading:
Abnormal Memory protection fault CS:EIP=000Ch:0009C8E5h
I don't use Anipro that much, but do need it on occasion. I could use
some help in getting it running again.
Here are my configs:
REM *******THE FOLLOWING LOADS KURTA PENSMITH******
C:
CD \KURTA
C:\QEMM\LOADHI /R:1 K_ISPS.COM
K_CHANGE.EXE -I
CD \
C:
REM *********END OF KURTA PENSMITH AUTOLOAD********
REM ***ADI PROTECTED DRIVER PATH****
SET DGPADI=C:\KURTA\DGKURTA2.EXP
REM ***END ADI PROT. DRIVER PATH****
PATH=C:\QEMM;C:\DOS;C:\WINDOWS;C:\MOUSE;%PATH%;C:\NU;C:\PCTOOLS\C:\NAV;C:\TPLUS
C:\TPLUS\winapp
PROMPT $p$g
SET NAV=C:\NAV
SET TEMP=C:\DOS
set hiip=c:\abekas
SET MGA=C:\MGA\SETUP\
REM ***ADI ENVIRONMENTS***
SET ACAD=C:\ACAD\SUPPORT
SET ACADDRV=C:\ACAD\DRV
SET ACADPAGEDIR=C:\ACAD\TEMP
SET ACADRV=C:\MGA\ACADRV
SET DSPADI=C:\MGA\ACADRV\RCMGA.EXP
SET RDPADI=C:\MGA\ACADRV\RCMGA.EXP
SET RCPADI=C:\MGA\ACADRV\RCMGA.EXP
set rcpadi=c:\prores3d\rcpr3069.exp
set vibcfg=c:\prores3d\vibrant.cfg
set rdpadi=c:\3ds2\drivers\rdptplus.exp
set vtpadi=c:\3ds2\drivers\vtpvlan.exp
REM ***END ADI ENVIRONMENTS***
TMODE 11
tpclr
c:
cd c:\mga\setup
c:\qemm\loadhi /r:3 mgavesa
cd \
c:
call c:\lantasti\startnet
DEVICE=C:\QEMM\DOSDATA.SYS
DEVICE=C:\SELECTOR\SELECTOR.SYS
DEVICE=C:\SCSI\ASPI7DOS.SYS /D
DEVICE=C:\QEMM\QEMM386.SYS rh:n ram x=c800-cbff x=d000-d8ff IB:Y ST:M
X=C000-C7FF X=CC00-CCFF X=CE00-CFFF X=F400-F4FF X=FA00-FAFF X=FC00-FCFF
X=FF00-FFFF R:2
DEVICE=C:\QEMM\DOS-UP.SYS @C:\QEMM\DOS-UP.DAT
DOS=HIGH
rem DEVICE=C:\QEMM\QEMM386.SYS ON MAPS=0
DEVICE=C:\QEMM\LOADHI.SYS /R:4 /SIZE=8592 C:\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP
SWAPSIZE=1024
REM DEVICE=C:\NAV\NAV&.SYS /B
DEVICE=C:\SCSI\ASPICD.SYS /D:ASPICD0
FILES=35
BUFFERS=35
LASTDRIVE=s
SHELL=C:\DOS\COMMAND.COM /P /E:640
DEVICE=C:\MGA\SETUP\RAMBIOS.SYS
DEVICE=c:\qemm\loadhi.sys /r:4 /res=10480 /sqt=fa00-faff /size=18944
C:\TPLUS\targap.sys md d6 i220
I have a Matrox MGA Impression 3ZV, AMI Enterprise III w/20megs RAM, Adaptec
2742 SCSI II controller, 2 Fujitsu HD's, Toshiba CD-ROM, Targa+, V-LAN, AE-2
ethernet.
Thanks for any pointers you could give me…
John Tissavary (La Luna cie)
Sheesh John, You got everything in one file. Make separate batch
files with the environment settings in each for the necessary
variables and clean them out at the end.
You have "%PATH%" in the middle of your path statement and all it does there is
copy the first part in again.
You have two DSPADI statements, three RCPADI statements and two RDPADI
statements. The last ones are overwriting the earlier ones.
I think you need to do some cleanup first.
Woops! I sent you an old autoexec.bak file by accident. I've got
the environments cleaned up, but still like to have them not as
separate batch files. I used to do that, but this is alot easier,
and each app uses a seperate one anyway (unless that's what's
screwing up anipro, but I don't think so).
Still wrong, but I could find only two rc* and to rd* statements.
Their remmed out of my current setup (I switch from time to time
depending on what I need to do in 3DS).
John Tissavary (La Luna cie)
If you have two occurences of the same environment variable (even
with different data attached) the second occurance is going to write
over the first. This means that if the application in question is
looking for that variable and needs the specific driver set in the
first instance, it's going to be handed the second one. Check it for
your self. Just type SET from the DOS command prompt and see what it
says.
Also since you haven't created a Command.com shell, I gotta assume that you're
also running out of environment space and not loading them all in.
I've definitely got Command.com and I had eliminated the redundancies (sent you
the wrong files) while optimizing my system, before I left the message to you.
There is no conflicting environment situation right now, but Animator Pro will
not allow me to enter the SCREEN SIZE menu. It kicks me out and give me BIG
DOS LETTERS:
Abnormal Memory protection fault CS:EIP=000Ch:0009C8E5h
I must stress that ALL other apps are working fine, and all hardware is doing
what it's supposed to. AniPro issue is the only thing that doesn't run. Also,
since memory is no longer an issue, I will retain all environments listed below
as part of my autoexec.bat. To make it easier to read the configs, I will
include a ";" followed by a description for anything that looks like it would
be a redundancy, or seems otherwise fishy <g>.
REM *******THE FOLLOWING LOADS KURTA PENSMITH******
C:
CD \KURTA
C:\QEMM\LOADHI /R:1 K_ISPS.COM
K_CHANGE.EXE -I
CD \
C:
REM *********END OF KURTA PENSMITH AUTOLOAD********
REM ***ADI PROTECTED DRIVER PATH****
SET DGPADI=C:\KURTA\DGKURTA2.EXP ; NOT DSPADI, this is a Kurta Tablet
environment
REM ***END ADI PROT. DRIVER PATH****
PATH=C:\QEMM;C:\DOS;C:\WINDOWS;C:\NU;C:\PCTOOLS\C:\NAV;C:\TPLUS;C:\TPLUS\winapp
PROMPT $p$g
SET NAV=C:\NAV
SET TEMP=C:\DOS
set hiip=c:\abekas
SET MGA=C:\MGA\SETUP\
REM ***ADI ENVIRONMENTS***
SET ACAD=C:\ACAD\SUPPORT
SET ACADDRV=C:\ACAD\DRV
SET ACADPAGEDIR=C:\ACAD\TEMP
SET ACADRV=C:\MGA\ACADRV ; _NOT_ ACADDRV environtment, this is a Matrox MGA
environment
SET DSPADI=C:\MGA\ACADRV\RCMGA.EXP
set rcpadi=c:\prores3d\rdpr3069.exp
set vibcfg=c:\prores3d\vibrant.cfg
set rdpadi=c:\3ds2\drivers\rdptplus.exp
set vtpadi=c:\3ds2\drivers\vtpvlan.exp
REM ***END ADI ENVIRONMENTS***
TMODE 11
tpclr
c:
cd c:\mga\setup
c:\qemm\loadhi /r:5 mgavesa
cd \
c:
call c:\lantasti\startnet
DEVICE=C:\QEMM\DOSDATA.SYS
DEVICE=C:\SELECTOR\SELECTOR.SYS ; this is a multiple boot configuration
utility. It has had no ill effects on apps at anytime. AniPro used to run
with this line included.
DEVICE=C:\SCSI\ASPI7DOS.SYS /D
DEVICE=C:\QEMM\QEMM386.SYS rh:n ram rom x=c800-cbff x=d000-d8ff IB:Y ST:M
X=C000-C7FF X=CC00-CCFF X=CE00-CFFF X=F400-F4FF X=FA00-FAFF X=FC00-FCFF
X=FF00-FFFF r:2 ; this exclusions were determined by QEMM 7.02. Anipro will
not run even with Stealth disabled.
DEVICE=C:\QEMM\DOS-UP.SYS @C:\QEMM\DOS-UP.DAT
DOS=HIGH
rem DEVICE=C:\QEMM\QEMM386.SYS ON MAPS=0
DEVICE=C:\QEMM\LOADHI.SYS /R:1 /SIZE=8592 C:\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP
SWAPSIZE=1024
REM DEVICE=C:\NAV\NAV&.SYS /B
DEVICE=C:\SCSI\ASPICD.SYS /D:ASPICD0
FILES=35
BUFFERS=35
LASTDRIVE=S
SHELL=C:\DOS\COMMAND.COM /P /E:640 ; this is the command.com shell
rem DEVICE=C:\QEMM\LOADHI.SYS /R:3 /SIZE=35712 C:\MGA\SETUP\RAMBIOS.SYS ; I'm
still experimenting with this vs. QEMM ROM option. Neither has a beneficial
effect on AniPro.
DEVICE=c:\qemm\loadhi.sys /r:4 /size=18944 C:\TPLUS\targap.sys md d6 i220
I do not believe there are any redundancies in my configs, and as I said
earlier, everything works (3DS, Fractal paint, ACAD, etc…) except for AniPro.
AniPro will let me do anything except change screen size.
Thanks for the help,
John Tissavary (La Luna cie)
John,
I've forwarded your message on to Grant Blaha who is Animator support for
Autodesk. Let's see if he can come up with something on this.
BTW…That's a real clean config.sys……<g>.
Thanks for forwarding the message. I don't frequent this part of the forum
that much, so I don't know who the best person is for AniPro questions.
John Tissavary (La Luna cie)
>>I've definitely got Command.com
What he meant is, in your config.sys, you didn't use a line like:
SHELL=C:\COMMAND.COM /e:700 /p
where the /e:700 means to expand the total environment size to 700 bytes, and
the /p is required to tell COMMAND.COM to execute an AUTOEXEC.BAT if it finds
one (this of course normally happens, but when you start putting things in a
SHELL= statement, you have to specifically tell it).
If you are trying to put more stuff (PATH + SET statements) into the
environment than there is room, the last stuff you try to put in is just
discarded.
Dave
PS, you can use the MFT program that comes with QEMM to tell you how much free
environment space you have.
Someone must have overlooked that line, because it was included. Even in the
incorrect config.bak I uploaded. I'm sure it was an oversight. I have E:640
in the line.
Thanks,
John Tissavary (La Luna cie)
I too looked at your startup files and thought they looked like redundant city.
Seemed like a file cabinet full with no folders.
Here's a technique I use to create the most efficient setup for different
operating sessions.
1. Create a dir called startup
2. Create another DIR called batch.
3. Do NOT list these in your path.
4. The last two lines in each autoexec.bat will be:
CD\batch
Type Menu.txt
5. an optional third line can state the startup mode eg:
Echo System started for WFW and scanner drivers
6. Create an optimized config.sys and autoexec.bat file pair for each of your
session modes. Locate them in the \startup dir. but name them with different
ext to denote the mode eg. config.scn for scanner and autoexec.scn as well.
7. In the \batch dir create a menu.txt as follows with any text editor.
STARTUP MODES:
1) WFW and scanner drivers
2) Lantastic Network
3) Clean boot no drivers
4) 3DS and targa+ drivers w/ QEMM
5) 3DS and targa+ drivers w/o QEMM
LAUNCH SOFTWARE:
10) 3ds with RDPADI renderer
11) 3ds with RCPADI renderer
12) 3ds with RDPADI & Diaquest VTR
20) Launch WFW with targa+
21) Launch WFW with SVGA TC
22) Launch WFW with SVGA 1024×768 256color
etc. get creative here because this will be your low level screen in dos
8. Create a batch file for each of the entries as follows:
@echo off
echo
echo
echo Copying startup files to root directory.
echo for reboot to Windows for Workgroups.
copy c:\startup\config.wfw c:\config.sys
copy c:\startup\autoexec.wfw c:\autoexec.bat
echo
echo
echo Hit CTRL-ALT-DELETE now to reboot!
Note: I wrote a small file called boot.com in debug that I put in instead of
the three finger command. It is listed as follows:
echo
echo Machine will reboot
pause
boot.com
Name the file 1.bat.
9. The launch files are done somewhat differently, might be simple or might be
complex as in 3DS + Diaquest launch:
d:
cd\3ds
set RCPADI=D:\3ds\drivers\RCPVESA.exp
set RDPADI=D:\3ds\drivers\RDPTPLUS.exp
set targa=248
rem load tconfig batch
call c:\targa\51248632.bat
call DQ50P
copy 3dsset.dq5 3ds.set
copy 3daditar.cfg 3dadi.cfg
3dshell
c:
cd\batch
cls
type menu.txt
Name this file 12.bat
10. Use the above examples to customize your entire system and
optimize a most efficient startup for each work session. The smaller
the startup files the better. You can even loadhi the stuff in the
launch files although this can be a bit tricky due to the
permutations involved. To additionally maximize efficiency I have a
number of 3DS.set and 3dadi files that I switch for 3DS. I also have
several win.ini and system.ini files although managing the windows
ini files gets cumbersom during new software installation. I haven't
figured a slick way to handle this yet other than manually copy and
paste
continued from #60849
I haven't figured a slick way to handle this yet other than manually copy and
paste using several windows of notepad at the same time. Time to call the real
programmers!
Final Note: My system is not exactly as above but I did the above as a general
ized approach by example for forum members to get the idea. It's an organized
approach to operating efficiency when switching among incompatible environments
that most of us deal with on this forum. Alan Iglesias said it best in a phone
conversation earlier this week: " If you insist on only one compromise startup
system for all your stuff then get a MAC. We have PC's and customizing them is
the advantage."
I've left a message with the correct configs to Joel (Sysop). The ones you
read were *.bak, used during optimizing my system. My environment variables
are not redundant: if you look closely they all point to different things.
Since memory is not a problem right now, I'll keep my environments as they are.
But if I need to add a lot more (hope NOT), I'll revert back to my old batch
file system, and will incorporate your tips, too.
The real question I've got (why I left the configs in the first place) is why
AniPro kicks me out when I try to change the screen size. I've got VESA
extensions enabled, so this should not be happening. I've tried with and
without stealth, but neither seems to work.
Thanks,
John Tissavary (La Luna cie)
Have you added any .DRV files to the RESOURCE subdirectory? I've seen
misbehaved drivers crash during the SCREEN SIZE operation.
>>Have you added any .DRV files to the RESOURCE subdirectory?<<
Not sure. I haven't changed anything on purpose, but will look into it.
Thanks,
John Tissavary (La Luna cie)
I'm not sure, but I think that I had to kill the QDPMI line before ANIPro
worked on my system. SOmebody here told me about it.
Chris
>>I'm not sure, but I think that I had to kill the QDPMI line before ANIPro
worked on my system<<
Thanks, I'll try it.
John Tissavary (La Luna cie)
You're right. Animator pro is NOT DPMI compliant.
I think that as soon as I dropped out that line ANI Pro started to work
immediately.
Chris
I just got 3D Studio R3 on Monday, so I haven't had a chance to try
the AniPro fix. But I'll get to it as soon as I pick my tongue back
up off the floor. The new renderer is phenomenal!
John: I just got my copy of 3DS R3 yesterday, but I don't have it
installed yet – I just got the disks backed up last night and I'll
probably install it tonight. I wish that they would make it
available on CD-ROM…
I agree, CD-ROM software installation would be great! But as Greg
said a while ago, they press the CD long before the release is ready
to ship. Maybe that'll change for R4.