CompuServe Thread

Ok, from the Shell try issuing the following series of commands: SETCLOCK RESET DATE 04-Mar-94 06:54:33 SETCLOCK SAVE The Setclock's RESET option forces a complete reset of the clock. This may be needed if a program turned off the clock or sets the test bit of the clock. The DATE command sets the date using a day-month-year, and a hour-minute-second format. Remember to change the date to your current date & time using a 24-hour clock. The final Setclock using "save" is the actual command that saves the time/date being "used" to the clock chip. Also, try checking the clock after certain programs are run. One of the programs may be crashing the clock. — JD >>I know that after I quit some programs I don't have the same memory I had when I started. […] Memory on the Amiga is dynamic. The Amiga can have memory added or removed from its " memory list" at any time. Not all the memory will be freed again immediately after a program is quit. The OS does preform memory flushs, freeing no-longer-being-used memory, as it is needed. Some memory isn't freed because the programmer failed to properly mark the memory as being freed. Another reason memory isn't always freed, is because it is being used to hold a ".library". The Amiga will hold a library in memory even after the program that loaded the library has quit. This allows the next program that uses that library, to do so without having to re-load it from disk. The OS will eventually delete the unused libraries from memory with a routine flush, or a request for a flush from AVAIL or WB. If you use "LoadWB -debug", in the startup-sequence instead of the normal LoadWB, you will be given an additional "developer menu options". One of these options is a flush command in the menu that forces the system to flush ALL unused libraries. — Don't worry about the RAM-disk, its existance is both normal and expected on the Amiga. There should be at least three special directories in the RAM-disk. They are: T: (holds temporary files generated by the AmigaDOS or other programs. The system's scratchpad) Clipboards: (temporyally stores text clipped by ConClip or other cut-n-paste programs like PowerSnap.) ENV: (the environmental varibles, copies of the WB prefs settings are stored here for quick reference. Other third party programs will use ENV: for their own config or pref files.) This RAM-disk is dynamic. If your files in the RAM-disk add upto to only 1K, then the RAM-disk is only 1K. If you put 786K in the RAM-disk, it will expand to 768K; as as you remove files, the RAM-disk will shrink back down again. — KD >>Is it possible for me to get the files needed to generate speech through the public domain?<< Through the PD, you can get sound & music files, their players, and even software that allows you to send commands to your CLI using your voice (requires additional hardware). You can also get software that *uses* Commodore's "Speech" software. You can't upload/download the Commodore "speech, narrator, and translater" files that Commodore shipped with 1.2, 1.3 & 2.0. Those files are copyrighted (and Commdore doesn't hold the copyright.) If you really want the Commodore speech files, you will need to either find and purchase the 2.0-disks, or "aquire" copies of these files from a friend. I have the files, but to tell the truth, I've only used them once or twice in the last three years. They aren't that well used. Ron. – ap'ing with AP. (Eagles may fly, but weasels aren't sucked into jet engines.)

you need to do a SetClock Reset command since your clock is totally confused. Then set the date and do a SetClock Save. As for memory, you won't always get back what you started with, even if you do an Avail Flush. There are myriad reasons, but a few are: the program didn't free up all the memory it allocated, a sign of a bad program; the resources allocated by one program are still in use by another program, if so, you won't get that memory back until the other program is finished with it; and simple differences in what was allocated between the start and end of the program, even if it frees everything up. Do NOT kill the RAM: disk. It is required by the system in AmigaDOS 2.04 or better, and highly recommended for AmigaDOS 1.3x. There are a lot of things tucked into the Ram: disk that have to be there in order to have your workbench setup the way you desire. If memory is a problem, it is definitely time to consider upgrading your system by a couple of megabytes, especially if your system is a stock A1200. Your system will run faster and you won't run into this problem unless you run a megaprogram. Your best bet for adding speach to your Amiga is to find a copy of AmigaDOS 1.3 or less somewhere and copy the relevent files off of it. If you need to know which ones, ask and I'll provide a list. So far as I know, there isn't a PD solution to this one. I hope this helps. "You do trust me, don't you? Of course you do." — "To Play the King" (BBC)