Printable View
Hi Friedrich,
All of a sudden I'm getting this error in SB 10 on my development VM.:
The file is there, exactly 32,000 bytes in size. I see there are
similar files in the SB7 and SB8 folders there. I renamed the file and
ran SB10 and it popped up a question about that it detected some SB8
settings and if it should import them. After it did that the file was
recreated.
I still have the file if you want me to send it to you for inspection.
Best regards,
--
Arnor Baldvinsson
Icetips Alta LLC
Hi Friedrich,
> All of a sudden I'm getting this error in SB 10 on my development VM.:
Forgot the screenshot:
Best regards,
--
Arnor Baldvinsson
Icetips Alta LLC
Hi Arnor,
> All of a sudden I'm getting this error in SB 10 on my development VM.:
Say "Thank You" to your protection vendor for a buggy update <g>
http://www.lindersoft.com/forums/showthread.php?46532
http://www.lindersoft.com/forums/showthread.php?32739
Friedrich
Hi Friedrich,
> Say "Thank You" to your protection vendor for a buggy update <g>
Sorry, no such thing in sight on this VM. As far as I know there was
nothing running on that VM when I ran SB. Backups run at night and I
can't think of anything that might have locked this file.
Interestingly when I compare a good .lic file with the bad one, the bad
one has the last 32 bytes of the good one repeated three times! See
screenshot from Beyond Compare in hex mode: http://screencast.com/t/yplZ4gER
Best regards,
--
Arnor Baldvinsson
Icetips Alta LLC
Hi Arnor,
The .lic is a standard TPS database. The "52" in Error "#2409/52" is
Clarion Error Code 52. It is definitely not caused by a bad file format.
"Something" (Microsoft Defender?) on your machine locked that file.
You can send me the .lic but I am pretty sure that it works fine here <g>
Friedrich
Hi Friedrich,
> The .lic is a standard TPS database. The "52" in Error "#2409/52" is
> Clarion Error Code 52. It is definitely not caused by a bad file format.
> "Something" (Microsoft Defender?) on your machine locked that file.
Indeed it was MD!!! I wonder why it locked that file but not the other
..lic files I created...
Best regards,
--
Arnor Baldvinsson
Icetips Alta LLC
Arnor,
>> The .lic is a standard TPS database. The "52" in Error "#2409/52"
>> is Clarion Error Code 52. It is definitely not caused by a bad file
>> format.
>> "Something" (Microsoft Defender?) on your machine locked that file.
>
> Indeed it was MD!!! I wonder why it locked that file but not the other
> ..lic files I created...
Let me tell you, I HATE COMPUTERS <g>.
Friedrich
Arnor,
> Indeed it was MD!!! I wonder why it locked that file but not the other
> ..lic files I created...
Because there was a specific byte combination in that unique TopSPeed TPS
database that looked like Devil's wife <g> and so MD was smart enough to
"lock" it (Danger, it's the signature of a virus).
Friedrich
Hi Friedrich,
> Because there was a specific byte combination in that unique TopSPeed
> TPS database that looked like Devil's wife <g> and so MD was smart
> enough to "lock" it (Danger, it's the signature of a virus). Friedrich
Yeah, I figured some such had happened. I think some AV work on some
computers and not others. I know that a lot of people have had issues
with AVAST. I have been using it for couple of years or so and have had
zero problems with it!<g> Others run X and Y and Z and never have
problems while others curse them. Just weird!
I remember back in the 90' I did a number of virus checks and removals
for customers in Iceland. Came on a 3.5" diskette, ran great and
REMOVED the bleeping things. It seems that now most of the AV can't
remove squat, they can only prevent infection, not fix it.
Best regards,
--
Arnor Baldvinsson
Icetips Alta LLC