#Unexplained Crash
2 messages in this thread
Brian:
Nice to hear from you. It's taken this long to get back to you because
it appears I've just figured out how to set the system to tell me if I've
got mail! I'm still rather new at AP. No, I haven't tried re-installing
yet. I wanted to get some advice first from someone like yourself. I kind
of thought the problem was file related, but had no idea where to start.
Like I said, everything was fine until suddenly I couldn't print anymore.
I've recently DL'ed all kinds of stuff, moved things around and had to
negotiate installing some of the DL'ed programs the old fashioned way —
meaning no point-and-click. I'm not very confident at this yet, and
figured I moved or deleted a file somewhere that controls printing.
Further, I thought maybe the problem was common or obvious enough for an
experienced user to say, "A-ha!" I still haven't been able to pinpoint the
glitch, and re-installing is the next step unless…
California: what's next…locusts?
Carson,
I've lost the parent of this message (hard drive crash here), so some
of this may be a repeat. Compare the contents of your l:, libs:, and
devs: directories against your master workbench diskette. See if any of
the sizes are different. Ignore any additional files on your harddrive
directories, they are almost certainly installed by some applications.
Next, check devs:Printers to see if your printer driver is in there.
If not, move it from sys:Storage/Printers over to devs:Printers.
Last thing, check to make sure the printer is selected in your
preferences settings and that you haven't done anything strange like
telling Preferences that you have a zero page size, etc. Double-check all
of those settings, even triple-check them.
I hope this helps. As for California, I believe locusts are due next
year, or the year after. They'll probably take the place of floods <g>.