PSN-L Email List Message

Subject: Re: Comma's
From: n0cwr@.........
Date: Sat, 01 Jan 2000 21:17:14 +0000

Thinking out loud.
If your able to read the files. What is different about your
hardware/software? I should be able to read them too.
What version and PC are you using?
I am using a 486DX50(WIN95)the SDR PC, 486DX120(WIN95) and P166(the WINNT PC
that receives the SDR save files over the network). I might mention again
that saving the file to disk and then looking at them on any of these PC's
and Winquake still see's them with a comma in front of the file name.

I tried Winquake v 2.5.2 and 2.4 32 bit versions on the 486DX120.
Only Winquake v 2.4 32 bit on the other two.
I have a Win95(486DX100), my daughters PC upstairs, and
a 386DX40 (WIN3.11) on the network here as well. The 386DX is used
for Packetcluster and ham radio databases.

This gives me some hope though. My file is useable. Just not by me! :) ha
But hasn't make the solution any more obvious at this point. 

At 12:29 PM 1/1/00 -0800, you wrote:
>Kevin --
>The files attached to your email were 000101a.ks1 and 000101b.ks1.  I don't
>know if you tried to send the ones that started with a comma, but when they
>got here they had no comma in the file name.
>I can open both files just fine with Winquake (v2.6.8).  Both appear to be
>identical, starting at 11:20:36 on 1/1/00.
>If the filenames you sent started with commas, you might try sending the
>files to yourself via email.  Maybe that'll strip the commas off.
>Next interesting thing:  I renamed the files (using NT4 SP3) and added a
>comma to the beginning of both the file names.  Winquake still opened the
>files without complaint, comma and all.  I've attached a .GIF file, which
>is a screen dump of Winquake with the ,000101a.ks1 file open.  Maybe your
>files have more than just a comma at the start.  Maybe there are some
>hidden characters too.  Do you have a program that can do a hex dump of
>sectors on a disk.  If you could look at the directory entry on a floppy
>for the file in question, you might be able to see more there than meets
>the eye.
>I seriously doubt that these files contain a contageous virus, since these
>aren't executable files and I don't think anyone would bother trying to
>make a virus for event files that could affect Winquake in such a way as to
>cause it to write bogus files.
>Be happy to work more on it later.  I'll be in and out for most of the
>afternoon. here.
>At 07:57 PM 1/1/2000 +0000, you wrote:
>>Thanks Karl!
>>Just got back home.
>>Lets try it and see what the file looks like to you.
>>Here's two saves. They look fine everywhere but Winquake 2.4.
>>SDR2.7 did the file save.
>>Winquake sees ,000101b.ks1 and ,000101a.ks1 and when you try to open
>>them it says ",000101b.ks1 was not found. (Of course! because DOS
>>WINNT4.0 SP3 or WIN95 SP1 see it as 000101b.ks1.
>>I ran NAV on these PC's. But please be sure to check them with your AV
>>I still am wondering about some Y2K virus writing a string to the files and
>>Winquake interpretating the file name differently.
>>I hate to think of updating motherboards. This WINNT pc is using a 166 and
>>it's the fastest PC in the house! There's just got to be a software fix.
>>Thanks Kevin
>>At 09:57 AM 1/1/00 -0800, you wrote:
>>>If someone wants to send me a file, I'll be happy to try to read it with
>>>Winquake.  Send it to me directly, not to the list.
>>Attachment Converted: "C:\Eudora\Karl's\attach\000101b.ks1"
>>Attachment Converted: "C:\Eudora\Karl's\attach\000101a.ks1"
>Attachment Converted: "F:\DOWNLOADS\wqfile.gif"


Public Seismic Network Mailing List (PSN-L)

[ Top ] [ Back ] [ Home Page ]

Larry Cochrane <cochrane@..............>