We are experimenting with using the REVELATION user for security purposes. Most things are working fine. However, there are some problems. I'm trying to do things to break the system.

* PDISK no longer works to the network (Yeah! – this is what we wanted)

* COPYTABLE encounters an error FS106 (access denied by the operating system). I suspect this is because the way the copytable works includes some DOS level stuff. Correct?

* To get around the problem with copytable, I tried using remaketable. One of the parameters of remaketable is volume name. I was hoping to be able to move a file to a different volume as you would with a copytable command with REMAKETABLE. However, orphan files were created. However, after the remaketable, the DOS file is reported to be unavailable on both the source and destination volumes. I've never tried using remaketable to move a file before, so I don't know if this is normal behaviour or not. Normally, I'd put the file right back where it was.

One final note. We are using HR-1 5.5 which reports Arev 3.02. Perhaps these problems have been corrected by version 3.12?

Greetings Victor,

I'll throw my 2 cents in with one of your problems: PDISK.

PDISK doesn't work with Win95 (I assume this). I think it has to do with the age of the assembler routine (SETPTR) that is called. I believe that Win95 has added a few more parameters to the internal printer definition/control blocks that deal with network paths and other status checks. The older routine doesn't take this into consideration. You will be able to PDISK once, but anything after that gets lost.

Others posts on this board show that this problem is prevalent and don't bode well for any AREV version since DOS based.

The workaround is to PDISK to a disk file and PCPERFORM a COPY to the desired captured device. PDISK seems to work fine for local printers and disk files. To print to a network printer you effectively do your own spooling. Since I'm in RevG I have more control over my printer redirection routines.

Some how you will need to accomplish this:

PDISK filename (8.3 filename convention applies)

print your report

PDISK PRN (closes the file)

PCPERFORM COPY filename LPTx (x=port#)

PCPERFORM ERASE filename (cleanup)

Done.

The upside is it works. The downside is that the report must complete before you can start printing. I design the topology around putting local printers on workstations that do the biggest reports. Short stuffs a breeze. Long stuff takes disk space. Considerations.

Can't help you with the other. Sorry.

Much Luck,

Charles Schmidling

DATASCAN Systems, Inc.

cbms@belnet.com

Copytable essentailly does a maketable, then OSREADS and OSWRITES out the file frame by frame. Security issues would definetly come into play here.

Remake, on the other hand, creates a temp file, then does a SELECT/READ/WRITE operation on the file. Since it deletes the old file and the temp file, there could be right related issues here as well.

akaplan@sprezzatura.com

Sprezzatura, Inc.

View this thread on the forum...