Finally again got the time to try to convert a 14-year-old Arev 3.12 app to Arev32 (WH).

Now I just can't get Arev32 to start properly. When it initially complains that a folder is unavailable I have been F5 and CW SETVOLUME to point the volume to the proper folder. Still having a problem with the VOC row named after the Application. Is it to be a volume pointer or to be a TCL batch script?

It would help if you could tell us where (and names) Arev32 startup references the environment, which VOC table, which startup TCL batch script?

Thanks,

Dave

Dave:

Start SYSPROG in OI and then exec the AREV32_STANDALONE_FORM

In OPTIONS-]APPLICATION enter the appname you converted and change the startup location to the path where your converted application is.

Then go into OPTIONS-]ENVIRONMENT-]GENERAL press shift-F1, select the environment for the converted application and change the default data location where ever the converted default data path is. You can edit this from OI actually in SYSENV appname_ENVIRONMENT. The application record in the first step above has checksum info in it so you may not be able to edit the record (I haven't tried it).

Perhaps it would be nice if the conversion process changed these paths? Maybe not.

The VOC startup {appname} record should be a type TCL record. The VOC file should reside in the path defined in the APPLICATION record defined above. These files get attached before any defined login process so the VOC login entries must be modified here. You can edit these from OI by doing an ATTACH_TABLE volume/path VOC then edit either LOGON or appname in VOC. Check to make sure LOGON exists in the VOC file. There was a hierarchy of how the startup processes were handled but I don't remember how it goes now.

Thanks Warren. I have to adapt my thinking because it didn't occur to me that I could bring up SYSPROG in Arev32 just like in Arev.

This helped a lot, but I found that the original programmer had modified the WINUS (menu) system to add some security. I now have to put it back to normal.

Dave

Success!

thanks to Warren A for the documentation on WINUS.

I had to create my own startup program in Arev32 because the original programmer had put security into WINUS, which is no longer used. He had renamed the RTI WINUS and replaced the SYSOBJ WINUS with his own. I couldn't find his renamed program.

also, I had to edit the startup script and remove all the ATTACHTABLE statements the pointed to the wrong folders. I used OI Database Manager to handle them.

Dave

Actually it was Ray Chan that sent the docs to you.

Can you get the ARev32 debugger to work for you? I couldn't get it to display the source code in the trace even when using the "SO fname programname" debugger command.

Hi, Warren. What response did you receive when you used the SO command? Did the debugger say that it couldn't find the source, or did it indicate it had loaded the source (but still didn't display it in the trace)?

Thanks,

- Bryan Shumsky

Revelation Software

I recall it did not complain but still would not display the source code. This is in a login security process called through the VOC TCL LOGIN entry where the attaches are being done.

Hi, Warren. As this was a security procedure, is it possible that it was compiled in a 'special' way to prevent the source code from being displayed?

Have you gotten into the debugger at any other time (either through an error, or through a DEBUG statement), and did the source trace work correctly at that time?

Thanks,

- Bryan Shumsky

Revelation Software

View this thread on the Works forum...