Gregy wrote:
>> My Win3.1 File Manager dates new year entries as "1/7/:0" instead of
>> the expected "1/7/00" What is the URL from which I can download the
>> fixing patch?
Fraser Farrell has them on his site:
FM for Win 3.1 -
www.dove.net.au/~fraserf/w31fman.zip
FM for Win Workgroups -
www.dove.net.au/~fraserf/wfwfman.zip
>> - A good backup discipline is my main protection from viruses, but that
>> "CMOS Boot Sector Write Alarm" seems a good tool to install. From
>> where? Otherwise I have used McAfee ever since infected with Monkey
>
>however,
>one of the "sharpies" on this list probably has the answer on the
>tip of his tongue, right now...<g> <g> <g.
:)
If you can switch to another BIOS this can be done. Either you need to
remove the BIOS chip (very easy - I've had more problem inserting ISA cards
than switching BIOSes, just be carefull so you don't bend the "legs" on it)
or if you're a little lucky the BIOS you have can be rewritten. I've no
idea if either of these are things you can do with your computer (read:BIOS).
>> several years ago, but the more recent issues seem beyond
>> installation for me. Besides that, a TSR Sentry seems to slow me
>> down too much. How susceptible are Arachnids anyway to infection?
>
>...someone recently answered my own question about this...you can
>check the recent digests for more detail....but, it boils down to
>----arachne is a DOS program....it doesn't sneak around in the
>background running things it has just downloaded from the net
>without waiting for you to tell it to....so...if you tell it to
>do something stupid...it will...otherwise your probably safe...
Precisely, there are of course risks with Arachne (as with any program) but
the chances that anyone will actually do anything is extremly small. First
of all you as a user must have made an active choice which wasn't very wise
(and no I'll not tell anyone what they are), secondly I doubt many users
(espacially those that might want to harm other people) actually can find
the weak spots an exploit them.
>> - Finally, a silly one. Years of correspondence files using my own
>> naming convention [eg "91231a}.arc"] to keep them in chronological
>> order whether incoming[{] or outgoing[}] has been thrown for a loop.
>> I have adopted "o" for the year for now, but there has to be a better
>> way!?
>
>...what is wrong with "01231a.arc", anyway...? it is your system..
>you are happy with it....why change now.....you're not coming down
>with an acute case of "post-y2k panic"...are you...? <g g g>
Use a, b, c etc. as the first "number". Then you'll be safe for 27 (or
something like that) years. By then you can probably start over from 0 - or
why not switch to using 0 now and backup all the files from before
somewere? Then every time the year has a 0 at the end you just back them
all up.
(Actually I noticed the same bug in the universitys user naming system,
someone who still was a student after 10 years would end up getting
information ment for people who just had started. But the normal case is 3
or 4 years for each student so that probably isn't a real bug).
//Bernie
http://hem1.passagen.se/bernie/index.htm DOS programs, Star Wars ...
