I found the following differences in the behavior of PDISK between AREV3.1 and AREV32.

1. In AREV32, if PDISK is unsuccessful in redirecting printer output to a file, the TCL level does not get reset. Try PDISK C:\XXX (which redirects output to the file XXX), vs. PDISK C:\ (which is an error because C:\ is a folder, not a file). There’s an extra TCL level that remains when that happens. There is no way to return to the original TCL level (i.e., ESC does not work). In AREV 3.1, the original TCL level is restored after the error message displays.

2. In AREV32, PDISK commands do not display on the TCL stack, while in AREV 3.1 PDISK commands do display on the TCL stack. This makes it difficult to find out exactly when a PDISK command was run.

3. In AREV32, PDISK with no leading space works. However if there are any leading spaces in the command, PDISK will not run.

:PDISK C:\XXX.TXT (works, no space between colon and command)

: PDISK C:\XXX.TXT (does not work, spaces between colon and command) Attached is a screen shot of the message produced. There is no way to correct the word. The only option is to press ESC.

In AREV3.1, as long as PDISK is the first word in the command string, PDISK will run.

4. In AREV 3.1, the (OS) options suppress the message that the file to which printer output is to be redirected already exists, or if for any other reason (e.g., the file is a directory or is in use), the output cannot be redirected. In AREV32, the error message displays.

My question is…has anyone else run into these differences? Should they be considered bugs because AREV32 should behave the same as AREV3.1? And if they are not bugs, are there any other differences between AREV3.1 and AREV32 (I saw differences in the debuggers, for example) that are documented?

Thank you.

Ira

Thanks to a quick response from Bob Orsini at Revelation Software, all the problems have been resolved. The problem is that my VOC was missing a PDISK item, with the entry:

RBASIC

SYSOBJ

PDISK

Thanks, Bob.

Ira

You can avoid running the command by calling SETPTR, instead.

I found this works in my version 9+ Arev32.

call setptr( device:char(0), ovr)

where device is a filename with full path, suffix of char(0)

where ovr=1 to overwrite

device can also be "PRN" to close the file, like PDISK "PRN"

Dave

I always pdisk to a local drive. Otherwise write caching can be an issue.

View this thread on the forum...