CompuServe Thread

#Image Processing R4

3 messages in this thread
#135286From: Evan Yares [WeirdTM]Nov 11, 1994 4:04 PM
I am trying to run a dealer copy of the Image Processing Routines for 3D studio with Release 4. The machine is a 486 DX4 with 32 megs of RAM running HIMEM.SYS for upper memory management. I can only successfully get the processes to run with a render display configured for standard 320×200 VGA. When I try to call the routines with 640×480 24-bit display my computer crashes. Also, when I tried to use 2 routines together (hilight and glow) under 320×200 VGA, the computer crashed as well. Is HIMEM.SYS sufficient to use with these routines? If not what should I do to get these routines working correctly? Steve Stogoski
#135293From: Jonas Ruikis [ADESK]Nov 11, 1994 4:23 PM
Hi Steve, My first question is, when in 3ds, and typeing a "?", does 3ds "see" all of your memory? << I am trying to run a dealer copy of the Image Processing Routines for 3D studio with Release 4. The machine is a 486 DX4 with 32 megs of RAM running HIMEM.SYS for upper memory management. I can only successfully get the processes to run with a render display configured for standard 320×200 VGA. When I try to call the routines with 640×480 24-bit display my computer crashes. >> If you set the render display to NULL, does it still crash when creating a file at that resolution? << Also, when I tried to use 2 routines together (hilight and glow) under 320×200 VGA, the computer crashed as well. Is HIMEM.SYS sufficient to use with these routines? >> You do not need *any* memory manager to run 3DS. It sounds like there is a conflict. Now to track it down…. << If not what should I do to get these routines working correctly? >> My first suggestion is to review your choices in 3ds vibcfg. What are they? Does this problem occur when you select Vesa Compatibles? Does it happen when you select the chipset instead of the current card choice? My next suggestion, if the above yields no results, is to examine your config.sys. For this next test, simplify your config.sys to only 2 lines, Files=# and Buffers=#. Your autoexec.bat should be a PATH statement and a load mouse. Do the routines work now? My next suggestion would be to verify that all of your RAM is working by performing any additional memory tests..
#135381From: Yost GroupNov 12, 1994 12:08 AM
Jonas hit the nail on the head. It sounds like you've got a serious incompatibility problem there. What happens when you don't use ANY memory manager? – G