CompuServe Messages

If the computer was rebooting while you weren't even there (I assume that means while it wasn't doing anything — just sitting there), that might indeed be a hardware problem. It is not at all usual for 3DS to spontaneously reboot. Such occurances, when they happen, usually mean that Studio and the computer's memory, TSRs, memory mangers, etc are in contention for memory resources. Or, put another way, something's not set up correctly. The most usual thing is that a memory manager and a video card are fighting it out with each other. For example, if you are using QEMM you might need to exclude certain portions of upper ram from QEMM's use (the QEMM manual has much more to say on this topic). It could also be caused, on some machines, from the computer's own memory caching or shadow ram; check the computer's setup to see if there is any of this you could experimentally turn off. ~The only other thing is some very scattered reports of reboots occuring with certain meshes. We are not sure what this is, as we can't reliably duplicate the condition. It might be related to some corruption within the .3DS file itself. This is extremely rare overall. ATO is meant to be run automatically. If you set up the forum options with the proper GO commands, etc, then it should work for you. You may have to log on manually, GO ASOFT, OPTIONS and change some of your default forum options before it will correctly thread messages for you. These settings should be covered in the ATO documentation. If this doesn't help, you can try over in the IBM forum (I think it is); that's where the primary support for ATO lives.