CompuServe Thread

#T-S and clock problem

2 messages in this thread
#51446From: Bill Christens-BarryJan 29, 1987 9:04 PM
I have a problem which seems to involve my T-S 2MB ram board. I wonder if any of you have had any similar problems with your board. Please help me if you can. The problem occurs at boot time (using 1.2). I have an A-Time clock on my parallel port, and in order to read the clock at boot time I have a command in my startup-sequence to "read-rtc". The file "read-rtc" was supplied with the clock in order for the Amiga to get the time and date info from the clock. In order to display the time I also run a clock program (either RSLclock12, RSLclock131, or klock2.0) in my startup-sequence (after the "read-rtc" command). The problem I have occurs during the startup-sequence at the point at which the clock command is encountered. I get a "software error -" and so on error box when this happens, followed by a guru visitation. The guru number is something like "xxxx3.020750". Now, what seems strange to me is that the error does not occur every time I boot! The crash occurs about 75% of the days when I first boot my Amiga. It occurs somewhat less often if I warm up the T-S board for maybe an hour or so before booting. If I do get the crash, a quick reboot will usually yiels a repitition of the problem. Usually I must boot three or four times before the problem clears up, turning the power off of the Amiga and the T-S board in between each boot attempt. I wonder if the problem is power supply related, since warmup seems to help. I should mention that my T-S board is otherwise fully operational (haven't checked the pass thru yet) and seems to have the more recent connector, altho without the cover. Did I mention that I have no problems at all if I remove the clock display pgm from my startup-sequence routine? The "read-rtc" pgm creates no problem, as I get no crash if I run it but not the display pgm. Can anyone give me some insight or suggestions regarding the solution to this problem? Thanks Bill Christens-Barry
#51469From: Jan 29, 1987 9:31 PM
Bill, Has your board a serial no. below 398 ? If yes, have you had your board upgraded otherwise problems like the described one is likely. Joergen