CompuServe Thread

#walking animals

3 messages in this thread
#177873From: Alan H. BondJun 29, 1995 8:23 PM
Since many four legged animals move in similar ways, usually with 3 or 4 gaits, walking, trotting, galloping, etc. I was wondering if someone has already solved the problem of making a 3D studio animated model, as a .3ds file? Incidentally, I still haven't solved my system hang problem, I have merely reached a higher state of consciousness where I realise that problems with bought systems are not solvable like program bugs, one rather tinkers with settings and parameters until something usable works. I got a new clean boot file from my computer supply friend which contains a himem statement as well as the files and buffers statements and this allows the system to actually load, and then it works for some renderings but still bombs out for others. Alan Bond
#177950From: Larry MintonJun 30, 1995 9:00 AM
I don't have sufficient memory to retain all that you have done to your system so far, so I'll go through a list of things I would probably do (in order). 1) run a memory test program. One that beats memory to death. 2) Map out all interrupts, roms, and i/o ports. ensure no conflicts 3) go into bios settings and turn off internal and external cache, any shadowed memory, and anything else that can be turned off. Also, check your motherboard manual and compare against your memory wait timing (something like 4-2-2-2). Some bioses don't allow you to do this. 4) pull every board off the motherboard, clean the contacts with an eraser, and reinstall only the boards absolutely necessary. 5) Borrow, steal, or beg another type of video card. 6) if hard disk controller is on a card, repeat step 4 for that card. 7) Repeat step 4 with the hard disk 8) Take a couple of big friends to whoever sold you the motherboard and request a new one. 9) Find a new line of work not involving computers. You are cursed. LAM
#177968From: David J. MarksJun 30, 1995 10:49 AM
>> still bombs out… It sounds like it might be time to get down to some real nitty-gritty hardware debugging. If you are not comfortable working inside your PC, (or if doing so will void your warranty,) please ignore this post. I can make no guarantees that this will help, but it may help isolate your problem. From your posts, I see that you have tried several "clean boot" scenarios. If you are still getting lock-ups or crashes, then it is likely not driver related. You should probably take some time to confirm that your master disks are not damaged. (ie Try installing on some other computer or have your dealer check and possibly replace them.) On to the hardware: I don't remember whether you posted your hardware specifics or not, but reposting them may help. Let me give you a rather vague description of the possible problems (as I see them). 1. Bad hardware… Faulty memory chips (sometimes very difficult to find) -or- bad Controller card (caching controllers are notoriously suspicious) -or- gremlins <g>! 2. Conflicting hardware… conflicting base addresses, IRQ's or DMA settings are the most common problems. Hopefully, you have other systems at your facility with which you can swap parts to find the problem -OR- you have a good dealer who will work through it with you. Determine the BARE MINIMUM configuration required to run your system. For instance, you don't NEED a cd-rom drive, sound card, tape drive, frame buffer, etc. If possible, temporarily remove those adapters. Check your results. Digging further, try a different brand controller card and check your results. Also, see if you can swap your SIMMS. If not, try to rearrange them and see if your system crashes at a different point in the rendering. Still further, try a different video card. Hopefully, you will find a situation that works correctly. Begin adding cards and drivers back one-by-one until you find the culprit. Try some voodoo rituals and magic dust, too… that always helps. – Dave