We have an old custom application written with Arev 1.1 on our NetWare server that we are decommissioning. The information in Arev 1.1 is just used for reference purposes. We would like to move it to a standalone PC.

I went into AREV BUMP and changed it from Advanced NetWare 2.0 Drv. 1.6 to Non-Networking Drv. 1.6 and copied the directory to the local drive. When I launched the application is says W504 Unable to ATTACH to SYS:DATA\BIOMED on Volume REVBOOT.

There is no-one left who knows how this application was setup or configured. If someone could point me in the direction on how to fix this it would be greatly appreciated.

Thank You

Susan Berezny

Susan,

It sounds like there is an explicit network map drive command in the logon script. You will need to remove this. Also, if it is mapping to a specified drive letter, and any of your processes use this drive letter, then you will have problems as the programs cannot access the specified drive.

You could possible work around this by using the SUBST command on a Windows PC. This allows you to associate a particular directory with a drive letter. This should make your application think that the drive letter exists.

There are others on this list with a lot more experience at this than myself. Hopefully they will chime in as well.

HTH,

[email protected]

this will be store in one of the following places

assuming you moved the files to the c drive and the directory is BIOMED

ED VOC LOGON

and change all references from SYS: to C:\

or it could be in

ED VOC account name

and change all references from SYS: to C:\

note: you probably dont need to change the network drivers on the stand alone Pc

Susan,

I just did this very thing last month and found that most of my problems were associated with volumes pointing to network resources. I used menu option Tools/Files/Set Volume. Then I got a list of all defined volumes by pressing F2. I then selected any volumes that pointed to a network drive and redefined them to point to the local drive. I logged off and everything worked when I logged back on.

Hope it helps,

Carl

I went into Tools/Files/Set Volume and it said "no F2 options available for Volume Name". But if I go to Tools/Files/Attach on Volumes I press F2 and see:

DOS

Indexing

Memory.Resident

Revboot

There must be somewhere in REVBOOT that has references to SYS:DATA\BIOMED, but I can't find it. It happens in the last of the 6 'dots' for launching Arev, when the REVBOOT volume is attached.

I was told that when the program is installed you tell it where the REVBOOT volumes resides, I just can't seem to change it. I've tried the Tools/Files/Name Media.

What is interesting is the program is now local to my hard drive with no network connection and I can go into REVBOOT and list files and there all there. But other than using AREV BUMP I cannot access the application. AREV (USER) just returns the error "Unable to attach to SYS:DATA\BIOMED on VOLUME Revboot.

It is likely a "logon" command that is attempting to attach the BIOMED info. This will also need to be copied local to your standalone machine.

After login press F5 to get TCL then F2 to see the "command stack". The most recent command will be number 1 on the list. Look down for something that says something like "LOGON" or "LOGON.ACCOUNT" or somesuch.

Press F5 again then type EDIT VOC LOGON or whatever the word was (if you don't see a word like LOGON just try LOGON ) and press enter. You should be in the editor with a record that says on line one TCL and on another of the lines ATTACH SYS:DATA\BIOMED.

You need to change this line to attach whereever you have copied the data to local - we'd suggest a subdirectory called DATA\BIOMED under your local AREV directory. Make the change, F9 to save then exit.

All should now be ok.

Keep us posted.

The Sprezzatura Group

World Leaders in all things RevSoft

Susan,

I believe that Matt and RWilson have the correct idea. There must be an explicit attach going on.

Try this, after you get through the error message press F5 for the TCL box and F2 for a list of executed TCL commands. Look for a command that has the form "USER.LOGON" where USER is the user name. The attach for SYS:Data\Biomed must be occuring in that user's logon script and should also appear in the list of executed commands.

If it is you'll know what VOC entry to edit.

Good Luck,

Carl

In addition to what the Sprezzies have suggested:

From SYSPROG check the USER/ACCOUNT settings to see what STARTUP/LOGON VERB is defined (Menu Trees Management - Accounts - Secure Account OR Management - Users - Secure Users).

If nothing is defined in the above then check the VOC for an entry that is the same name as the ACCOUNT or USER or LOGON (ie EDIT VOC BIOMED)

Do a LISTVOLUMES and then a LISTMEDIA on each of the listed VOLUMES as there maybe a VOC file for the ACCOUNT in the REVBOOT and some other VOLUME. If this is the case then do an ATTACH REVBOOT VOC and search that file for the above items.

In desperation time (granted you are running under Windows) you can always use the Window FIND utility, starting from your AREV folder on files REV*.* containing text SYS:DATA\BIOMED and then relate the REVxxxxx (and directory) back to the VOLUME and FILE in AREV. Or create a symbolic AT.REC in VOC with code as follows:

@ANS=@RECORD

CONVERT @LOWER.CASE TO @UPPER.CASE IN @ANS

Then do a: SELECT VOC WITH AT.REC "SYS:DATA\BIOMED"

Given any hits follow this with: EDIT VOC

You can use this technique on any program files also.

Susan

Since you have not replied to the other posts stating that you had solved the problem I thought I'd chime in here. I'm still happily working in AREV 1.16 and use it every day for a number of my own apps.

If you would like to ZIP the AREV Folder and email it to myself or any of the other respondents I'm sure we could quickly identify the offending entry and offer some concrete solution.

Depending on the size of the ZIPped file you could also ZIP the entire APP and email that. Confidentiality assured !!

My email is [email protected]

Happy to assist.

Regards

I was unexpectedly away since last Thursday. I will try all the new suggestions today and post how things worked. Thank You! Susan

Thank you for your offer, it is very generous. I was away since last Thursday so I will try the new suggestions first and get back to you if it still doesn't work! Susan

Thank you for everyone's help. The application now works on a standalone PC. In the login script BIOMED.LOGON there was an ATTACH to SYS:DATA\BIOMED.

Susan Berezny

View this thread on the forum...