#Renderize & ATI GPT
15 messages in this thread
Since I installed an ATI Graphics Pro Turbo 4 Mb VRAM in my machine, Renderize
gives me a GPF at 0005:12AE. Is there anything that I can do to avoid this
crash with the macx.drv from ATI. I have talked to ATI tech twice with no help.
Thanks,
Jim Cross
Do you have the DeviceBitmap=off statement in the mach64 section of your
WIN.INI?
– Jeremy Kumin, Written 30-Dec-1994 @ 10:13:34
Using: Windows NavCIS PRO 1.25
>>Do you have the DeviceBitmap=off statement in the mach64 section of your
WIN.INI?
Yes, I have had it on and off. It still gives the exact same message. The GPF
is at 0000:12AE unless I have started and closed some other app. It then will
be very near the same location. Renderize is, at the present time, the only app
that I have crashing there. I have had other GPFs since the GPT installation
that have crashed with the same error message in this area of memory. It is
always because of the ATI macx.drv. Is there any to keep Renderize from
accessing this block of memory?
Thanks,
Jim Cross
Does Windows state the mach driver in the GPF msg? Of is it GPF in module
[unknown]? Can you upload to my mail (74431,3611) your config.sys,
autoexec.bat and the first 20 lines in win.ini? I'll look at it and call you
(be sure to include your phoneno).
Best regards,
Nick Josephs
Visual Software
>>Does Windows state the mach driver in the GPF msg? Of is it GPF in module
[unknown]?
It states macx.drv.
>>Can you upload to my mail (74431,3611) your config.sys, autoexec.bat and the
first 20 lines in win.ini? I'll look at it and call you (be sure to include
your phoneno).
Yes.
Config.sys (I've tried QEMM 7.04, DOS's Himem.sys, NOEMS, etc. with no effect
on the GPF).
DEVICE=C:\QEMM\DOSDATA.SYS
DEVICE=C:\QEMM\QEMM386.SYS NOEMS RAM x=0000-00FF X=C000-C7FF ARAM=C800-CCFF
x=F000-FFFF R:2
DEVICE=C:\QEMM\DOS-UP.SYS @C:\QEMM\DOS-UP.DAT
rem DEVICE=C:\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP SWAPSIZE=16384
lastdrive=Z
rem DEVICE=c:\NDW3\NAVTSR.EXE
dos=high,umb
DEVICE=C:\QEMM\LOADHI.SYS /R:2 /SIZE=15200 C:\DTCSCSI\ASPI3X70.SYS
DEVICE=C:\QEMM\LOADHI.SYS /R:2 /SIZE=12208 C:\DTCSCSI\ASCSI.SYS
DEVICE=C:\QEMM\LOADHI.SYS /R:2 /SIZE=8880 C:\DTCSCSI\ADTC-CD.SYS /D:DTCCD
stacks=9,256
FCBS=4,4
rem DEVICE=C:\DOS\SMARTDRV.EXE /DOUBLE_BUFFER
BUFFERS=3,0
FILES=99
DEVICE=C:\QEMM\LOADHI.SYS /R:1 /SIZE=4848 C:\WINDOWS\IFSHLP.SYS
DEVICE=C:\QEMM\LOADHI.SYS /R:1 /SIZE=14032 C:\DOS\SETVER.EXE
SHELL=C:\QEMM\LOADHI.COM /R:2 C:\DOS\COMMAND.COM C:\DOS\ /e:1024 /p
DEVICE=C:\QEMM\LOADHI.SYS /R:2 /SIZE=12160 E:\PROAUDIO\MVSOUND.SYS D:3 Q:5
Autoexec.BAT
PATH
c:\mouse;C:\DOS;C:\WINDOWS;c:\mach64;c:\PS;c:\NDW3;C:\QEMM;C:\;C:\MDB;C:\XTPRO;
:\ALDUS;D:\PM4;\ALGOR;C:\PR;c:winword
C:\QEMM\LOADHI /R:2 C:\DOS\MSCDEX.EXE /D:DTCCD /l:g /M:8
C:\QEMM\LOADHI /R:2 /LO C:\WINDOWS\SMARTDRV.EXE /v C+ D+ E+ G 2048 128
C:\NDW3\IMAGE.EXE
SET SYMANTEC=c:\NDW3
VERIFY OFF
PROMPT $P$G
SET TEMP=c:\windows\temp
set mouse=c:\mouse
c:\qemm\loadhi /r:2 /lo c:\mouse\mouse
c:\qemm\loadhi /r:1 C:\DOS\doskey
C:\WINDOWS\net start
Win.ini
[windows]
spooler=yes
NetWarn=1
NetMessage=Yes
run=
load=C:\MOUSE\POINTER.EXE C:\ATI\ATIDESK\ATIKEY.EXE
NullPort=None
BorderWidth=3
CursorBlinkRate=530
DoubleClickSpeed=500
Programs=PIF EXE BAT COM
Documents=doc txt wri xls xlc sam jw jwt tg1 qw qwt
DeviceNotSelectedTimeout=15
TransmissionRetryTimeout=45
KeyboardDelay=2
KeyboardSpeed=31
ScreenSaveActive=0
ScreenSaveTimeOut=420
CoolSwitch=1
MouseThreshold1=0
MouseThreshold2=0
Thanks Nick, I use Renderize quite a bit. I bought the GPT card for Renderize.
Jim Cross
(317)533-2070
Jim, it looks as if you have not excluded the area A000-C7FF as recommended by
ATI. This is their "stock" answer for exclusions, although many folks can get
away with using C000-C7FF. Also are you shadowing ROM on the video (either via
QEMM or your Systems BIOS)?
I'm using QEMM 7.5 and my command line for QEMM looks something like this:
DEVICE=C:\QEMM\QEMM386.SYS DBF:2 RAM ST:M SUS:N X=A000-C7FF X=D000-D3FF R:3
You might want to try contacting ATI directly in their forum. Matthew and
Allan are pretty good about responding to inquries (so long as they are
directly answerable). Where they are sometimes less than responsive is if the
inquiry requires research.
Hope this helps a little — I know it VR Can be run with the GPT and with QEMM
7.04, QEMM 7.50 – 7.52, and with HIMEM/EMM386 since I have loaded/run it each
way. Good luck and have a safe and happy holiday.
Regards,
– Jeremy Kumin, Written 30-Dec-1994 @ 16:41:45
Using: Windows NavCIS PRO 1.25
>>Jim, it looks as if you have not excluded the area A000-C7FF as recommended
by ATI. This is their "stock" answer for exclusions, although many folks can
get away with using C000-C7FF.
The x=C000-C7FF exclusion was at the suggestion of ATI tech. Shure enough, QEMM
excludes A000-BFFF whether you tell it to or not. I've had A000-C7FF excuded
for years, I think that I will do it again.
>>Also are you shadowing ROM on the video (either via QEMM or your
SystemsBIOS)?
Viseo ROM no, system ROM is enabled and not configureable on my EPA motherboard.
I suspect that may be the problem.
>> You might want to try contacting ATI directly in their forum. Matthew and
Allan are pretty good about responding to inquries (so long as they are
directly answerable). Where they are sometimes less than responsive is if the
inquiry requires research.
I believe this one may require research. The macx.drv is throwing the monkey
wrench in my gears. I have had a message posted in the ATI forum for 2 days
now. I have called ATI tech 3 times now and the problem remains the same.
>>Hope this helps a little — I know it VR Can be run with the GPT and with
QEMM 7.04, QEMM 7.50 – 7.52, and with HIMEM/EMM386 since I have loaded/run it
each way. Good luck and have a safe and happy holiday.
I haven't tried 7.5 QEMM but Renderize ran great until the ATI GPT.
Thanks Jeremy, Happy New Year to you.
Jim Cross
Jim:
Your problem may be related to one of 2 things:
Devices and programs loaded into high memory. I know that you need to load
some stuff high in order to run the GPT in hi-color modes, but it might be a
worthwhile experiment to disable DOS-UP.SYS so that things get loaded low, then
run the GPT in a 256 color mode to see if things work better.
Disk cache. I noticed that your smartdrive buffer is only 128K for Windows.
Do you have a hardware cache? More likely, have you enabled 32-bit file access
in the 386Enhanced, Virtual Memory area of Control Panel? If it is enabled,
disable it and increase your smartdrive cache to see if things work better.
There are some other possbilities that come to mind, but these two warrant
research before we move on.
Please let me know if this helps, and if it doesn't, we'll take the next step
together.
Nick Josephs
]Visual Software
Nick,
>>Devices and programs loaded into high memory. I know that you need to load
some stuff high in order to run the GPT in hi-color modes, but it might be a
worthwhile experiment to disable DOS-UP.SYS so that things get loaded low, then
run the GPT in a 256 color mode to see if things work better.
I have fired up with minimum boot files and the results are exactly the same. I
did try your above suggestion again, same thing.
>>Disk cache. I noticed that your smartdrive buffer is only 128K for Windows.
Do you have a hardware cache? More likely, have you enabled 32-bit file access
in the 386Enhanced, Virtual Memory area of Control Panel? If it is enabled,
disable it and increase your smartdrive cache to see if things work better.
Makes NO difference! It makes no difference it I start WFW without the network
drivers(an extra 1.5 Mb of RAM left) and the same problem. I have a new minimum
installation of Windows on another drive that still generates the same GPF.
I found a thread on the ATI forum talking about pixel depth and icon cache.
Something about a maximum of 12 icons per group at 24-bit res. I have reduced
icon count with no aparrent help. I thought maybe the extra icons generated by
Renderize might be causing the problem but even the minimum Windows
installation didn't correct the problem.
I have found that if I hold the I key for about 15 seconds to Ignore the GPF
that Renderize will load. It will even run if I hold the I key every time that
Renderize does an operation. It acts like the system is resetting all icons and
then running. Could the Icons cause the GPF?
Thanks Nick,
Jim Cross
Nick,
>>
Your problem may be related to one of 2 things:
Devices and programs loaded into high memory. I know that you need to load
some stuff high in order to run the GPT in hi-color modes, but it might be a
worthwhile experiment to disable DOS-UP.SYS so that things get loaded low, then
run the GPT in a 256 color mode to see if things work better.
ATI just released an updated driver (1.44) for the mach64 series GPT cards. I
can now load Renderize with no GPFs. If I try to load a project that is complex
WFW reports a GPF in EYES.EXE at 0001,BD4F. If I start a project with the same
Objects and minimal additions it will render.
Would more physical memory help? I ahve 16 mb but only about 5.5 mb left after
loading Windows. If I start WFW without the net drivers I have about 7 mb left
but the GPF still is there. My GDI DLL starts at over 1.5 mb and grows to over
2 mb after launching a few apps.
Would an upgrade to Renderize Live help? I am using V 2.0. If so, is the
upgrade still $99 for the package?
The 1.44 ATI drivers are much more stable but I still have a few crashes with
Renderize and a some other minor glitches. I don't expect another driver for a
while and need to stabilize Renderize., I use it a lot.
Thanks again Nick,
Jim Cross
>>I am using V 2.0<< Renderize 2.0??? Aha!
This is almost definately the ol' big bitmap problem, solved in Renderize v2.1.
I think that upgrading your version to something more current will solve your
problem. I'm not sure what the upgrade policy is, p[lease call our marketing
office at (800) 669-7318: they can help.
Nick Josephs
Visual Software
Nick,
>>This is almost definately the ol' big bitmap problem, solved in Renderize
v2.1. I think that upgrading your version to something more current will
solve your problem.
Is 2.1 available to owners of 2.0? If it fixes bugs it should be. Can I
download a fix?
Thanks again,
Jim Cross
Jim:
Version 2.1 is no longer available. We're currently shipping Renderize Live
version 3.1. Please contact our sales office at (800) 669-7318 and speak to
Kevin, our Sales Manager, to discuss upgrading from 2.1 to 3.1, since we don't
have a "policy" for this upgrade.
Nick Josephs
Visual Software
Nick,
I ordered the Renderize Live upgrade yesterday. Loren said that RL 3.2 would be
released in 2 weeks and that she would wait to ship until then. I shure hope it
fixes my GPF on entry when the project is complex. You said that the fix for my
problem was in Renderize 2.2 I haven't been able to use Renderize since
installing the ATI GPT 4 Mb catd in late December. My rendering is backing up.
Thanks,
Jim Cross
Jim:
Yes, the new version will work fine on the GPT 4MB. However, if memory serves
me right the GPT has its own animation codecs, so to generate animations you'll
need to re-install the animation drivers from ATI after installing Visual
Reality.
Nick Josephs
Visual Software