CompuServe Messages

I have had R4 for a couple of months, now, but have not been able to get it to work on my PC, though R3 runs like a champ using the same configurations. I have upgraded my DOS to 6.22 and QEMM to 7.5, have tried with optimized configurations and manual ones, used HIMEM.SYS and EMM386.EXE instead of QEMM and stripped my boot files to nothing more than path, prompt, mouse and memory manager, all to no avail. I have a Micronics 486/66 VLB and a Diamond Stealth Pro. I have 52 MB RAM which QEMM recognizes all of. I have 2 420 MB IDE drives with an on-board VLB controller. R2.0, R2.01a and R3 all run great on my machine. When I first installed R4, it said 3DS.MLI was invalid. I eventually deleted R4 and reinstalled. It said 3DS.MLI was invalid, again. I opened R3 and did a /surface/material/get library and opened the R4 library with no problem. I tried various configurations. I deleted R4 again and reinstalled. This time it did not complain about the library, but would not open a project file larger than about a Meg. When it did it redrew the screen at about 1/2 the speed of R3. When I tried to open larger files, it would lock up so CTRL-ALT-DEL would not do anything. Once, it said that there was insufficient RAM to open my project file and it would do a partial open. It then locked up. I restarted and opened it in R3, no problem. When I take everything out of my CONFIG.SYS and AUTOEXEC.BAT except mouse driver, DOSKEY and QEMM, R4 locks up without displaying a cursor. If I use 3DS VIBCFG to get in, I get in and have a mouse, but when I try to open a project it locks up. When I put my SCSI and sound drivers back into my config files, R4 opens with the aforementioned limitations. I have downloaded posted discussions of the video driver problems people have had with R4 and tried every suggestion – eliminating ratholes from QEMM, etc. – with no success. Has R4's means of access the hardware changed that much that my very compatible and common configuration no longer works, or is it possible that my copy of R4 is bad? Especially with the way it instantly claimed its library file was bad after installing. It's hard to believe you changed that much code so much that R4 is useless on this computer when R3 runs so well. Here are my config files. Can anyone help? AUTOEXEC.BAT @echo off PROMPT $p$g path C:\UTIL\QEMM;c:\;c:\dos;c:\batch;c:\util\add2dos;C:\dps_par c:\util\qemm\loadhi /r:1 doskey c:\util\qemm\loadhi /r:2 c:\util\mouse\mouse c:\util\qemm\loadhi /r:2 c:\dos\mscdex /d:cdrom2 /v /l:f /m:1024 SET TEMP=D:\ set grasp=c:\GRASP set pictor=c:\GRASP CONFIG.SYS DEVICE=c:\util\micronet\mndosm.sys /p330 /d device=c:\util\qemm\dosdata.sys DEVICE=C:\UTIL\QEMM\QEMM386.SYS FRAME=NONE RAM R:1 DISKBUF=2 device=c:\util\qemm\dos-up.sys @c:\util\qemm\dos-up.dat DEVICE=C:\UTIL\QEMM\LOADHI.SYS /R:1 /SIZE=8880 C:\UTIL\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP SWAPSIZE=1024 DEVICE=c:\util\qemm\loadhi.sys /R:1 c:\util\micronet\mncdrom.sys /d:cdrom2 DEVICE=c:\util\qemm\loadhi.sys /R:2 c:\util\micronet\mnmdisk.sys DEVICE=c:\util\qemm\loadhi.sys /R:2 c:\proaudio\mvsound.sys d:3 q:2 j:0 t:1 DEVICE=c:\windows\smartdrv.exe /double_buffer BUFFERS=40,0 FILES=40 DOS=HIGH,UMB LASTDRIVE=Z FCBS=4,0 STACKS=0,0 SHELL=C:\COMMAND.COM C:\ /P David {Anxious and frustrated} Taffet