duc@csd4.milw.wisc.edu (Duc Minh Tran) (01/19/89)
[ What are these line eaters I keep reading about? ] Anyone out there with a Michigan Software Insider? The clock on mine cannot seem to store the correct date; it always runs one day or 24hrs late. Here is how I set the Insiders clock: 1) Use the Date command to set the Amiga's current date & time. 2) Use RTClock -W to write the previous info to the Insider clock. When I use RTClock -R (read the date & time) off of the Insider, the info would be correct. Now if I re-boot and then type RTClock -R again the date and time displayed would be 24hrs late. I (going for a long shot) even used a clock virus dectector but Amiga does not recognize the Insiders clock. I would appreciate any suggestions on a cure. ---------------------------------------- | I'm a schizophrenic! | "Internet" duc@csd4.milw.wisc.edu | The opinions expressed are not mine. | "UUCP" ihnp4!uwmcsd1!uwmcsd4!duc ----------------------------------------
koo%loki.edsg@hac2arpa.hac.com (frances koo) (01/20/89)
Did you try using Kickstart 1.1? I remember having some problem
setting the clocks and I think I finally did it using the old
Kickstart.
Let me know if you still have problems.
- Franceshull@hao.ucar.edu (Howard Hull) (01/22/89)
In Article 30751 of comp.sys.amiga duc@csd4.milw.wisc.edu (Duc Minh Tran) says: >[ What are these line eaters I keep reading about? ] While frequently encountered a few years ago, they are now nearly extinct. The problem was caused by a bug in readnews or inews or some such utility. The bug was manifested whenever the first character of the first line was a tab or a blank. The manifestation was in the form of the removal of about the first 512 or 1024 characters of a submitted forward response. The fix was to whip 7178 sites into updating their news software, and in the meantime, inserting [some (usually) inane remark] on the first line of any article that had been submitted from a troff or nroff processor (which pretty-prints the text in indented all-the-same-length lines). Now let's get down to business. >Anyone out there with a Michigan Software Insider? Yep. > The clock on mine >cannot seem to store the correct date; it always runs one day or 24hrs >late. Enter wise guy mode: If it can store any date from this century, it can store the right date from this century. Read on. > Here is how I set the Insiders clock: >1) Use the Date command to set the Amiga's current date & time. Allowably due to circumstances which are no fault of yours, this is nonetheless your first mistake. 2) Use RTClock -W to write the previous info to the Insider clock. That's what I do, too. >When I use RTClock -R (read the date & time) off of the Insider, the >info would be correct. Yes, that's what happened to me on my first reboot, January 1, 1989, too. > Now if I re-boot and then type RTClock -R again >the date and time displayed would be 24hrs late. Me too. And a great circus of events at my house followed that. Picture me trying to determine the state of my sanity when I wasn't even sure I had started the year sanely. > I (going for a long shot) >even used a clock virus dectector but Amiga does not recognize the Insiders >clock. And, lucky for us, neither do the virus codes. > I would appreciate any suggestions on a cure. Ok. Here's a pragmatic solution: 1. Invoke the AmigaDOS Date command in a fashion that sets the AmigaDOS clock to a time 24 hours in the future. 2. Issue the command RTClock -w 3. If you have a line in your Startup-Sequence that reads RTClock change it to two lines that read RTClock >NIL: Date or RTClock >NIL: C:Date or RTClock >NIL: :c/Date or whatever correctly PATHs your AmigaDOS Date command. Now you are OK until the _next_ time you need to set your clock from your favourite/favorite standard. But by then "you know the drill." 4. Write or call Michigan Software and ask for an update to your RTClock binary that doesn't have this annoying bug. Maybe we can get them to post it (or a patch) to the net, maybe, huh, pretty please, maybe? Alternatively, suffer through until Bush gets re-elected, and then you can add TWO days to the clock-setting procedure (takes care of government induced temporal inflation). Here's an address and telephone number: Michigan Software 43345 Grand River Novi, MI 48050 (313) 348-4477 > ---------------------------------------- >| I'm a schizophrenic! | "Internet" duc@csd4.milw.wisc.edu So also is your Michigan Insider RTClock software. Which reminds me: Your insider may some day need another dose of Lithium. That is, after Quail is elected pres, you will again need to get out your Insider documentation and fix your eyes upon the following - "The INSIDER Memory board also features a Real TIME CLOCK with a 10 year built in lithium battery, the battery is non-replaceable and should give you trouble free service for many years." Boy, is Michigan going to be surprised - `You have an Amiga WHAT? Er, granpa told me about those...' >| The opinions expressed are not mine. | "UUCP" ihnp4!uwmcsd1!uwmcsd4!duc > ---------------------------------------- Nor mine. Maybe they are a transcendental expression from Michigan Software, who, with the Insider, can be congradulated for one of the most successful Amiga 1000 products for all time... Howard Hull hull@hao.ucar.edu
sneakers@heimat.UUCP (Dan "Sneakers" Schein) (01/22/89)
In Message <463@csd4.milw.wisc.edu>, duc@csd4.milw.wisc.edu (Duc Minh Tran) writes: >[ What are these line eaters I keep reading about? ] > Something that has not existed for years, yet people keep feeding them. >Anyone out there with a Michigan Software Insider? The clock on mine >cannot seem to store the correct date; it always runs one day or 24hrs >late. Here is how I set the Insiders clock: > 1) Use the Date command to set the Amiga's current date & time. > 2) Use RTClock -W to write the previous info to the Insider clock. >When I use RTClock -R (read the date & time) off of the Insider, the >info would be correct. Now if I re-boot and then type RTClock -R again >the date and time displayed would be 24hrs late. I (going for a long shot) >even used a clock virus dectector but Amiga does not recognize the Insiders >clock. I would appreciate any suggestions on a cure. > I remember seeing messages about this on a commercial network. Turns out there is a bug (?) in the INSIDER clock program. A fixed version has been released (I know its on PLINK & BERKS AMIGA anyway). Sneakers -- Dan "Sneakers" Schein {pyramid|rutgers|uunet}!cbmvax!heimat!sneakers Sneakers Computing 2455 McKinley Ave. Of course heimat is an Amiga. West Lawn, PA 19609 Doesn't everyone run UUCP & UseNet on an Amiga? Call: BERKS AMIGA BBS - 60+ Megs - 24 Hrs - 12/2400 Baud - 215/678-7691
mjm@beach.cis.ufl.edu (Michael Murphy) (01/24/89)
In article <463@csd4.milw.wisc.edu> duc@csd4.milw.wisc.edu (Duc Minh Tran) writes: >Anyone out there with a Michigan Software Insider? The clock on mine >cannot seem to store the correct date; it always runs one day or 24hrs >late. Here is how I set the Insiders clock: Well, this isn't helpful, but i've been curious about similar behavior. My Insider clock acts wierd too, but not as predictably as yours. I can get it to store the correct date, and recall it reliably many times, sometimes even for weeks. But then one day the system will boot up and the date will be way off, for no apparent reason. I can usually reset it once (sometimes requires twice), and it will work for awhile. I never really figured it out, because i got a Supra 4x4 harddrive interface, and it has another battery clock, so i just started using it and forgot about the other... -Michel Murphy mjm@beach.cis.ufl.edu -- -Michael Murphy mjm@beach.cis.ufl.edu
Hurn@cup.portal.com (Edward Hurn Braswell) (02/03/89)
Ahh.. the dreaded clock got you, too! I've had my insider for about 2 years now (maybe a little longer?), and the clock worked just FINE until Jan 01, 1989. This year, when I reboot, and it RTClock's the Real Time Clock time into the system clock/date, it subtracts 1 day during the process. My solution? I set my Insider clock to run 1 day fast. This way the REAL date is read into the system clock. Anyone from Michigan Software know any better solution? -Hurn Smith-
24847843%WSUVM1.BITNET@cunyvm.cuny.edu (Shawn Clabough) (02/28/89)
I just recently started having a problem with my clock in my 2000. Does
anyone know what could be the problem. When I execute 'Setclock load'
it returns 'Battery Backed up Clock not found'. I have heard of a clock
virus, was there any truth to this?
Shawn Clabough
24847843@WSUVM1.BITNETjlabelle@lynx.northeastern.edu (08/15/90)
I just bought A3000. When I boot the 1.3.2 Workbench, it doesn't seem to load the internal clock, which doesn't let me know the time in AMAX. There is certainly a command: SetClock load I tried to copy SetClock load on the 2.0 side and found the computer giving me a worse error. HelP! Thanx. -JML- p.s. Please reply via mail - since I do not get on enough to search for messages concerning this. ------------------------------------------------------------------------------- Where's my CDTV?