V133JR65@UBVMSC.CC.BUFFALO.EDU (Julian Wixson) (08/21/89)
I recently got a no-slot-clock and have had no problems as far as compatibility with any programs I'm using it with. However when I run Mr. Fixit in Test Mode on my hard drive it find errors in the modification and creation dates which have been written to the disk after I got the clock. Then when viewing the catalogs with ProSel and inverse block appears before the time, but everything works perfectly. ProDOS has no problems with it so I just wondering why ProSel's Mr. Fixit would have any problems with the dates and times written to the disk. If anyone has any ideas please let me know. --Julian
S840802@UWEC.BITNET (TODD GEORGE) (08/28/89)
I am using an Apricorn No-Slot-Clock, and for some reason Pro-Term, and
everything else I try, will not read the seconds off of the Clock.
It reads the Date/Hour/Minute perfectly. Does anyone Know what the problem
could be? Any help/Patches would be great.
Thanks
Todd George
S840802@UWEC.BITNET
T.G.<--------------------------------------------------------------------->D.M.S840802@UWEC.BITNET (TODD GEORGE) (08/28/89)
Message received and acknowledged. T.G.<--------------------------------------------------------------------->D.M.
JerryK@cup.portal.com (Jerry E Kindall) (08/29/89)
Re: the no-slot-clock's inability to read seconds...
That's because almost all programs call ProDOS to find out what time it is.
ProDOS doesn't return seconds. It's that simple.
If you want to read seconds, you could write your own driver, but expecting
publishers to put special drivers into their programs to read seconds from
every conceivable type of clock would be silly. (Grin)
/\ Jerry Kindall | JerryK@cup.portal.com
\/ Death to COBOL | GEnie: A2.JERRY ALink: A2 Jerry
The answer that evades our brains, we only think we're wearing chains
-- Utopia