maddie@pnet01.CTS.COM (Tom Schenck) (09/28/87)
Someone out there is using JClock? Hope you don't have an SCSI hard-drive!
UUCP: {cbosgd, hplabs!hp-sdd, sdcsvax, nosc}!crash!pnet01!maddie
ARPA: crash!pnet01!maddie@nosc.mil
INET: maddie@pnet01.CTS.COMkhayo@sonia.UUCP (09/28/87)
In article <1783@crash.CTS.COM> maddie@pnet01.CTS.COM (Tom Schenck) writes: >Someone out there is using JClock? Hope you don't have an SCSI hard-drive! I am; I don't; but why? Pray elaborate (I think I can guess, though...) ----------------------------------------------------------- >>>>---------------> khayo@math.ucla.edu
hammen@csd4.milw.wisc.edu (Robert Joseph Hammen) (09/28/87)
>Someone out there is using JClock? Hope you don't have an SCSI hard-drive! Over the past couple years, I have seen references to the fact that JClock is 'a known killer of hard drives.' I personally have used JClock all of the time on virtually every machine (except the Mac II) with and without hard drives. I have never had a disk crash (hard or floppy) with it installed, and have had no problems with it at all. I think that it is time that this rumor about it end, unless someone can come up with evidence that JClock destroyed his disk. BTW, everyone using System 3.2 or later should really take advantage of the JClock INIT resource that you simply copy into your System Folder. That way you don't have to run an application to install it and use ResEdit to remove it. What probably happened to someone is that they ran the JClock installer to put the INIT in their System file and their System file was damaged for some reason or another. >UUCP: {cbosgd, hplabs!hp-sdd, sdcsvax, nosc}!crash!pnet01!maddie >ARPA: crash!pnet01!maddie@nosc.mil >INET: maddie@pnet01.CTS.COM Robert Hammen Computer Applications, Inc. hammen@csd4.milw.wisc.edu Delphi: HAMMEN GEnie: R.Hammen Robert Hammen Computer Applications, Inc. hammen@csd4.milw.wisc.edu Delphi: HAMMEN GEnie: R.Hammen
dlt@csun.UUCP (Dave Thompson) (09/28/87)
In article <1783@crash.CTS.COM> maddie@pnet01.CTS.COM (Tom Schenck) writes: >Someone out there is using JClock? Hope you don't have an SCSI hard-drive! Why? I'm using on a Mac+/HD20SC and it works just fine--though it doesn't on MacII. -- Dave Thompson uucp: {ihnp4|hplabs|psivax}!csun!dlt CSUN Computer Center phone: (818) 885-2790 18111 Nordhoff Street, Northridge, AdFDGV5)H
chow@batcomputer.tn.cornell.edu (Christopher Chow) (09/28/87)
In article <2953@uwmcsd1.UUCP> hammen@csd4.milw.wisc.edu.UUCP (Robert Hammen) writes: >>Someone out there is using JClock? Hope you don't have an SCSI hard-drive! > >Over the past couple years, I have seen references to the fact that JClock >is 'a known killer of hard drives.' I personally have used JClock all of >the time on virtually every machine (except the Mac II) with and without >hard drives. I have never had a disk crash (hard or floppy) with it installed, >and have had no problems with it at all. I think that it is time that this >rumor about it end, unless someone can come up with evidence that JClock >destroyed his disk. I too, have used JClock for quite a while, with both floopy and hard disk systems, and have yet to experience a JClock related crash. However, there are good reasons for NOT using JClock: 1. JClock just writes to the menu bar w/o checking for things which are there. Most notably, Pyro! dosen't work very well with JClock since Pyro! will blank out the screen, but JClock will continue to write the time on the upper right hand corner (of an Plus/SE/512k). 2. JClock dosen't check screen size, so it in the wrong place on a Mac II (I know this can be patched, but it then won't work on a Plus/SE/512k) It also appears in the wrong place or outright dosen't work with some virtual large-screen INITs for the very same reason. So what should you use for a clock? I use Menu Clock 3.0 - it works with virtual large-screens, Pyro!. I think it'll also work on a Mac II, but I don't have one to test. Junk JClock - use "correctly" written software! Christopher Chow /---------------------------------------------------------------------------\ | Internet: chow@tcgould.tn.cornell.edu (128.84.248.35 or 128.84.253.35) | | Usenet: ...{uw-beaver|ihnp4|decvax|vax135}!cornell!batcomputer!chow | | Bitnet: chow@crnlthry.bitnet | | Phone: 1-607-253-6699, USPS: 7122 N. Campus 7, Ithaca, NY 14853 | | Delphi: chow2 PAN: chow | \---------------------------------------------------------------------------/
ir353@sdcc6.ucsd.EDU (Matthew Grayson) (09/29/87)
> >So what should you use for a clock? I use Menu Clock 3.0 - it works with >virtual large-screens, Pyro!. I think it'll also work on a Mac II, but I >don't have one to test. Junk JClock - use "correctly" written software! > >Christopher Chow Here here! Menu Clock 3.0 works very well. It's unobtrusive, shares the menu bar with switcher and multifinder without collision. It hides behind screen savers, positions itself correctly, and it DOES work without flaw on a MacII. Rah! Matt
corwin@apple.UUCP (Someone Else) (09/29/87)
In article <2953@uwmcsd1.UUCP> hammen@csd4.milw.wisc.edu.UUCP (Robert Hammen) writes: >>Someone out there is using JClock? Hope you don't have an SCSI hard-drive! > >Over the past couple years, I have seen references to the fact that JClock >is 'a known killer of hard drives.' I personally have used JClock all of >the time on virtually every machine (except the Mac II) with and without >hard drives. I have never had a disk crash (hard or floppy) with it installed, >and have had no problems with it at all. I think that it is time that this >rumor about it end, unless someone can come up with evidence that JClock >destroyed his disk. Just to make this complete, I have used JClock on a Mac II... While it doesn't crash (as long as you don't try to remove it), it doesn't behave exactly as advertised either... I installed JClock, and rebooted, as nothing seemed to happen. A while later, I noticed some glitches at the top center of my menubar. I looked real close, and yep, there it was, JClock --- the only problem was that it was using something like one or two point type. Other than that one "tiny" glitch, it worked fine (tho it is no longer on my system) -cory -- Disclaimer: It's all just Illusion! UUCP: {sun,voder,nsc,mtxinu,dual}!apple!corwin CSNET: corwin@apple.csnet
russ@oakhill.UUCP (Russell Schwausch) (09/29/87)
In article <2485@batcomputer.tn.cornell.edu> chow@tcgould.tn.cornell.edu (Christopher Chow) writes: > >There are good reasons for NOT using JClock: > >1. JClock just writes to the menu bar w/o checking for things which are > there. Most notably, Pyro! dosen't work very well with JClock since > Pyro! will blank out the screen, but JClock will continue to write > the time on the upper right hand corner (of an Plus/SE/512k). > >2. JClock dosen't check screen size, so it in the wrong place on a Mac II > (I know this can be patched, but it then won't work on a > Plus/SE/512k) It also appears in the wrong place or outright dosen't > work with some virtual large-screen INITs for the very same reason. > >So what should you use for a clock? I use Menu Clock 3.0 - it works with >virtual large-screens, Pyro!. I think it'll also work on a Mac II, but I > >Christopher Chow I have been using JClock.31, the init you put in the system folder, for several months with no problems in a system with a hard disk. I just put it on 2 Mac SE's at work with Pyro. I first tried something called MenuTimeInit but the time stays on the screen when Pyro blanks it. With JClock.31 I can at least turn off the time by click on it but this isn't ideal. Is Menu Clock 3.0 something different or a newer version of MenuTimeInit? I WOULD like something that works with BIG screens because we are getting 2 SuperMac SuperView monitors installed today. Where can I get Menu Clock 3.0? -- Russell Schwausch, Motorola Inc., OakHill, Tx. (A suburb of Austin) UUCP: {harvard,ihnp4,seismo,gatech,nbires}..!ut-sally!oakhill!russ Ma Bell: (512)440-2426 It's a ticket agent, it's a fare collector, no ... it's SUPERCONDUCTOR!!!
ching@amd.UUCP (09/30/87)
I can not substantiate the rumor to any degree furthur than to say that I was having random crashes while backing up my hard disk (can't say if any other problems were due to JClock). I heard the rumor and removed JClock and have not had a crash during backup since then. I have never had my hard disk trashed by JClock. mike ching
joseph@cooper.UUCP (09/30/87)
in article <770@csun.UUCP>, dlt@csun.UUCP (Dave Thompson) says: > > In article <1783@crash.CTS.COM> maddie@pnet01.CTS.COM (Tom Schenck) writes: >>Someone out there is using JClock? Hope you don't have an SCSI hard-drive! > > Why? I'm using on a Mac+/HD20SC and it works just fine--though it doesn't > on MacII. > Some kind soul has just installed JClock on our Mac SE/HD20 system. Even though it is nice to have the clock on the menu bar, the system has responded slower while running applications. For example, using SuperPaint, if I select an object in the Draw layer and drag it, I have to wait a few seconds before the object starts to move even if I am dragging it using the outline. So, my question is: How do I remove it from the system??? Joe Gunoz cmcl2!phri!cooper!joseph "The answer to the ultimate question of life, the universe, and everything is ... forty two."
loucks@intvax.UUCP (Cliff Loucks) (09/30/87)
in article <2485@batcomputer.tn.cornell.edu>, chow@batcomputer.tn.cornell.edu (Christopher Chow) says: > > So what should you use for a clock? I use Menu Clock 3.0 - it works with > virtual large-screens, Pyro!. I think it'll also work on a Mac II, but I > don't have one to test. > While it's nice to have a clock automatically pop up (as an INIT), I now run Juggler (MultiFinder hasn't made it to Albuquerque yet) and put the Alarm Clock display where ever I want it on the screen. It fits very nicely between the menu bar and the HD20 icon on the desktop. -- Cliff Loucks [gatech | ucbvax]!unmvax!sandia!intvax!loucks Sandia National Labs, Albuquerque, New Mexico Poor New Mexico; So far from Heaven, and so close to Texas.
waltervj@dartvax.UUCP (walter jeffries) (09/30/87)
In article <1783@crash.CTS.COM> maddie@pnet01.CTS.COM (Tom Schenck) writes: >Someone out there is using JClock? Hope you don't have an SCSI hard-drive! Is this or a nasty bit of rumor mongering or what? Do you often yell fire in movie houses (or conversely, 'movie in a fire house' :-) If you have some reasoning and facts to back this 'statement' up then please do share it with the rest of us... I for one have been using JClock with 9 SCSI hard-drives for over a year w/o any problem that haven't been traced to other things.
lsr@apple.UUCP (Larry Rosenstein) (10/01/87)
In article <336@intvax.UUCP> loucks@intvax.UUCP (Cliff Loucks) writes: > >While it's nice to have a clock automatically pop up (as an INIT), >I now run Juggler (MultiFinder hasn't made it to Albuquerque yet) >and put the Alarm Clock display where ever I want it on the screen. >It fits very nicely between the menu bar and the HD20 icon on the >desktop. WIth Multifinder, you can make the Alarm Clock automatically appear when you boot. The only problem is that it will appear at a fixed place on the screen, so you will have to move it to the position you want. One of the options under Set Startup is to startup and launch the currently open applications and DAs. -- Larry Rosenstein Object Specialist Apple Computer AppleLink: Rosenstein1 UUCP: {sun, voder, nsc, mtxinu, dual}!apple!lsr CSNET: lsr@Apple.com
waldman@endor.harvard.edu (benjamin Waldman) (10/02/87)
In article <1783@crash.CTS.COM> maddie@pnet01.CTS.COM (Tom Schenck) writes: >Someone out there is using JClock? Hope you don't have an SCSI hard-drive! I've been using JClock for a week on my SE with 20MB internal SCSI (I have it as an INIT file in my System folder). Ben Waldman waldman@endor.harvard.edu
hammen@csd4.milw.wisc.edu (Robert Joseph Hammen) (10/05/87)
In article <1041@cooper.UUCP> joseph@cooper.UUCP (Joe Giannuzzi) writes: > >So, my question is: How do I remove it (JClock) from the system??? There are two varieties of JClock floating around. The most recent version is sometimes called "JClock.31", has a cute icon, and is installed by placing it in the System Folder of your startup disk. Open up the System Folder, look for a file called "JClock" or "JClock.31", and trash it. The next time you boot, it should not appear. If you don't have a file called "JClock" in your System Folder, you have two options: 1)If you have a copy of ResEdit and are not afraid to use it, do the following: Run ResEdit. Open up the affected System Folder, select the System file, and open it. Look for the resource type INIT and open it. Find the one that looks something like this: INIT "JClock" =4 and select it (the ID# might not be the same). Then, go to the Edit menu and select Clear. Click on the close box for the INITs, and then click on the close box for the System file. Save the changes when it asks you. Voila, the next time you reboot, it should be gone. 2)If you don't have ResEdit or if you do but are afraid of it, look for a small public domain program called "Remove JClock." I know it is available on CI$, and I have a copy of it, but have no upload/download access at this site. Remove JClock will perform the above surgery on your System file for you. Robert Hammen Computer Applications, Inc. hammen@csd4.milw.wisc.edu Delphi: HAMMEN GEnie: R.Hammen