CompuServe Thread

Problems with TS 1.04

12 messages in this thread
#11110From: Mateen GreenwayMay 1, 1995 3:04 AM
Hi, I'm hoping you could help me with a coule of problems I'm having with TS 1.04. The first is that when working with large or complex models my machine hangs (i.e., the mouse cursor stops responding) and then my machine reboots itself. I occaisionally get Out of Memory errors but very rarely. I'm running TS on a Pentium 90 with an Intel PCI motherboard with 16 meg of RAM and a 2meg SPEA-V7 Mirage graphics card. I'm using Windows 3.11 and it's set up with a 30 meg permanent swap file. The display uses the SPEA Bigwin driver set to 800×600 in 65,000 colours. I was thinking of upgrading the memory in the machine to 24 meg this month. The second problem I have is that over the last week or so when I edit an object, save it and reload it some of the pieces have moved. Is there something wrong with the way my axis are set? If I then move the pieces to the correct location again and save it they stay in the right place until the next time I edit the object. The other question I have is about the upgrade to TS 2.0. I bought TS in February this year so I understand that I am eligable for a free upgrade. I even managed to find the purchase receipt for it. the thing is, I'm in the UK so how do I go about getting hold of the upgrade and when is it likely to be available. Thanks in advance for your assistance. Regards Mateen
#11142From: CaligariMay 1, 1995 4:15 PM
Ok…. Here are my thoughts on the reboot prob. It looks like a fetal memory error in windows (which is not displayed). The error could be coming out of the graphics driver or another driver that is getting hosed. The system memory becomes unstable when you put that kind of demand on it (due to a weak driver) and poof BIOS version number or C:\. Here are some suggestions…. 1. You need to isolate what is causing the problem. Do this by selectively elimating drivers from the system. Load/remove them one at time and try to recreate the crash. 2. Consult the graphics card vendor on any know problems on the windows platform. They may know of some. As far as the scene reload problem. We have heard of this before but no one has been able to recreate it. It, as of yet, has not happened to us. If you can recreate the problem or have the scene that it happened to plz upload it. To get the free upgrade send in your receipt and reg card and we will contact you about receiveing it. –=R=–
#11148From: Frank IppolitoMay 1, 1995 5:51 PM
>>looks like a fetal memory error<< Hi Guys, Is this like: "I forgot I was supposed_to_be_born ? <G>
#11161From: Terry Cotant[RSS]May 1, 1995 10:45 PM
>> Is this like: "I forgot I was supposed_to_be_born ? <G> ROFL..
#11169From: Ian FirthMay 2, 1995 12:53 AM
PMJI, but Mateen might want to look at available low DOS memory. His reboot crash sounds like EMM386 puking without an error code. Things to look for… Leaky video card drivers, out of date VxDs, fat TSRs… $0.02 Ian
#11347From: Mateen GreenwayMay 4, 1995 3:27 AM
Ian, >>available low DOS memory<< I'm running with about 570k DOS memory does this sound too little? Regards Mateen
#11385From: Ian FirthMay 4, 1995 5:53 PM
Mateen, >I'm running with about 570k DOS memory does this sound too little? That's before Windows loads. After Windows loads you will have much less. My systems usually have around 180k-210k available after Windows is up, but that can drop dramatically depending on what apps are running. When it hits zero (as it does here when using Premiere), bang! out to DOS. Norton Utilities 8.0 has a nice sys meter that shows remaining DOS mem plus many other nice to know items. Someone here may know of another, possibly, shareware utility that will do the same. Regards, Ian
#11403From: Kenneth M. RiegerMay 4, 1995 9:33 PM
Hi Ian-yup, you've got to watch your resources! I use a Windows app called "Statline" (picked it up as STAT32.ZIP) that runs as a little status bar in Windows. It has quite a few settings for determining what you want to keep your eye on. I've set mine up with date/time/system resources/total&virtual memory so that I know when I'm pushing the system close to it's limit. Handy for avoiding crashes. …Ken
#11416From: Ian FirthMay 5, 1995 6:10 AM
>"Statline" (picked it up as STAT32.ZIP) Does it report low DOS memory from Windows? Ian
#11519From: Kenneth M. RiegerMay 6, 1995 12:13 PM
|->>"Statline" (picked it up as STAT32.ZIP) Does it report low DOS memory from Windows?<-| No, Ian-unfortunately not. I find that the "resources" status in % is enough to keep me out of trouble. I picked up a great little freeware program called "SAW" (System Analyser for Windows) that reports on the status of your entire machine and O/S (including DOS). This is the only program that's been able to accurately dig into my machine (it's not that fancy) and tell me what's going on. It even has a visual/audible alarm setting to warn you when you're pushing things a bit too far. Sometimes you get more than you payed for! <g>. …Ken
#11599From: Andrey ZmievskiyMay 7, 1995 4:52 PM
>>I picked up a great little freeware program called "SAW" (System Analyser for Windows) that reports on the status of your entire machine.<< Where did you get it? -= Andrey =- ZIPtag * Zen T-Shirt: Enlightenment Available – Enquire Within
#11661From: Kenneth M. RiegerMay 8, 1995 12:25 PM
|->>>I picked up a great little freeware program called "SAW" (System Analyser for Windows) that reports on the status of your entire machine.<< Where did you get it?<-| I picked it up off a local BBS. I just checked, and I don't seem to have the zip file on my drives any more. I think it was probably "SAW.ZIP" or something like that. The program is called "The System Analyst for Windows" and I have ver1.01. It's freeware, and copyright C. A Silasi 1992-1995, SiSoft Software. If you can't find it, let me know and I can re-locate it for you. …Ken