NOT READY READING DRIVE F (AREV Specific)
At 31 JUL 2000 11:25:59AM mike balchin wrote:
We recently moved from Novell to NT.
Drive F under Novell was the network drive with arev on it.
The workstation with this error has now drive F mapped to a CD.
When going into the application manager the above error comes up with the normal dos options, if you select F (fail) five times it goes in OK.
This error only occurs if there is no CD in the CD drive.
If going into the application directly the above errors do not occur and it does not matter if a CD is in or out!!
Somewhere ther must be a pointer to drive F at the masnger level.
Odd !!!
Anyone seen this before
At 31 JUL 2000 11:36AM Don Bakke wrote:
Mike,
This could be hidden in a number of places. However, I would first look at the following:
1. From SYSPROG check out the application system and data directory paths
2. Look at the application startup command record in VOC to see if it is attaching files from this drive
3. See if you have a quick attach referencing files from this drive
At 31 JUL 2000 02:34PM Don Miller- C3 Inc. wrote:
Also .. from your app:
SELECT VOC WITH F1=VOLUME"
LIST VOC F2 F3 F4
This will give you any volume pointers that may be used to attach the app. Also, it is probable that indexes may point to a Drive Letter (depending on which version of AREV you used).
Don Miller
C3 Inc.
At 31 JUL 2000 03:06PM Steve Smith wrote:
Check the AREV rollout paths and sort paths from the SYSPROG account.
At 01 AUG 2000 02:32PM Warren wrote:
NT Disk Administrator allows you to remap volume/drive letters. Change the CD-ROM drive to some other letter and then assign F: to the appropriate drive/volume.
Start - Programs - Administrative Tools (common) - Disk Administrator.