Utility for checking .CAS files

[zephyr]

Thanks Rob, will test it over the next few days and let you know if there are any problems.

Regards,
Steve

[zephyr]

The backup copy it makes of the original .cas file is corrupt.

Regards,
Steve

[robcfg]

Which version are you trying? Just to see if this is a system-specific bug.

I tested it yesterday and I think the backup was fine.

Can you upload the two files so I can dig into it?

[zephyr]

Sorry Rob, I was mistaken. Everythings OK...

Regards,
Steve

[zephyr]

Hi Rob,

Just a quick to let you know that I have tested it quite thoroughly to date, and there's been no problems so far.

Regards,
Steve

[robcfg]

Hi Steve,

Glad to hear it works ok and that it's useful.

If you have any further suggestions, don't hesitate to tell me.

Best regards,

Rob

[Sarah]

I'm sure I have seen one around... maybe an option on an existing tool like DC ??

Just browsing an old topic, but thought I'd answer anyway!

Yes DC converts anything you like to CAS format; it's the default behaviour - no option needed!

Its sister tool WHATIS also provides an analysis for lots of file types of that period, including block and checksum verification for CAS files.

Here's a quick session script showing binary and ASCII examples:

Code: Select all

C:\dragon> whatis /v screen.d14

VERBOSE DESCRIPTION
===================
File Length:    6144 bytes

SUMMARY
=======
SCREEN.D14 is possibly a .D14 Dragon PMODE3/4 screendump.

C:\dragon> dc screen.d14
=BINARY=
Writing SCREEN.cas
C:\dragon> whatis /v screen.cas

VERBOSE DESCRIPTION
===================
Blocks In Program 1:
    001  Type: 00  Length: 14  Status: ok (extra length)
         File Name: "SCREEN  "
         File Type: Machine Language (Start=0600; Exec=0167)
         Signature: Dragon Convert V4.00
         Source:    Pure Binary
    002  Type: 01  Length: FF  Status: ok
    003  Type: 01  Length: FF  Status: ok
    004  Type: 01  Length: FF  Status: ok
    005  Type: 01  Length: FF  Status: ok
    006  Type: 01  Length: FF  Status: ok
    007  Type: 01  Length: FF  Status: ok
    008  Type: 01  Length: FF  Status: ok
    009  Type: 01  Length: FF  Status: ok
    010  Type: 01  Length: FF  Status: ok
    011  Type: 01  Length: FF  Status: ok
    012  Type: 01  Length: FF  Status: ok
    013  Type: 01  Length: FF  Status: ok
    014  Type: 01  Length: FF  Status: ok
    015  Type: 01  Length: FF  Status: ok
    016  Type: 01  Length: FF  Status: ok
    017  Type: 01  Length: FF  Status: ok
    018  Type: 01  Length: FF  Status: ok
    019  Type: 01  Length: FF  Status: ok
    020  Type: 01  Length: FF  Status: ok
    021  Type: 01  Length: FF  Status: ok
    022  Type: 01  Length: FF  Status: ok
    023  Type: 01  Length: FF  Status: ok
    024  Type: 01  Length: FF  Status: ok
    025  Type: 01  Length: FF  Status: ok
    026  Type: 01  Length: 18  Status: ok
    027  Type: FF  Length: 00  Status: ok (EOF)

SUMMARY
=======
SCREEN.CAS is a .CAS virtual cassette file containing a machine language
program called "SCREEN" (generated by DC from a pure binary file).

C:\dragon> whatis /v waffle.txt

VERBOSE DESCRIPTION
===================
All 1579 characters in the file are printable.

SUMMARY
=======
WAFFLE.TXT is perhaps just a text file.

C:\dragon> dc waffle.txt
=ASCII=
Writing WAFFLE.cas
C:\dragon> whatis /v waffle.cas

VERBOSE DESCRIPTION
===================
Blocks In Program 1:
    001  Type: 00  Length: 14  Status: ok (extra length)
         File Name: "WAFFLE  "
         File Type: ASCII BASIC
         Signature: Dragon Convert V4.00
         Source:    Text File
    002  Type: 01  Length: FF  Status: ok
    003  Type: 01  Length: FF  Status: ok
    004  Type: 01  Length: FF  Status: ok
    005  Type: 01  Length: FF  Status: ok
    006  Type: 01  Length: FF  Status: ok
    007  Type: 01  Length: 60  Status: ok
    008  Type: FF  Length: 00  Status: ok (EOF)

SUMMARY
=======
WAFFLE.CAS is a .CAS virtual cassette file containing an ASCII BASIC program
called "WAFFLE" (generated by DC from a text file).

C:\dragon>