USE already assigned to network share

[mrc2048]

Hi

With the latest version of vDos (5/30/18) when I start vdos from a network drive drive c: is already assigned to the vdos startup directory and I cannot change it to the root of the drive as I would prefer.  THe only solution I see is to put vdos.exe int he root which is not ideal.  Is there a way to re-assign a drive using the USE command.  

Thanks

[mrc2048]

Slight correction - the drive c: is assigned to the current directory not to the directory vdos is in so even copying vdos to the root and entereing \vdos does not fix the problem - i have to cd to \ and then run vdos. this is definitely new compared to older versions of vdos and breaks all our systems that use it - help!

[Jos]

I don’t quite follow: If you start (double click) vDos with for instance Windows Explorer in some directory, that directory will become the current directory, and is by default assigned to vDos C:. If you use a shortcut with a “Start in” directory set, that will be used. Nothing has been changed to this logic over the years.
Also, you can re-assign the vDos C: drive. Though only once and under certain conditions, like no open files on that vDos drive.


Mind, assigning a vDos drive letter to the Windows root file system isn't a good idea. Your program could attempt to perform actions Windows prohibits.

Jos

[mrc2048]

with the old version of vdos if i go to the cmd prompt and cd to the directory i want to start in and type net use i get



D:\PUB\vdos>net use

New connections will be remembered.



Status Local Remote Network

-------------------------------------------------------------------------------

OK D: \\ds2014\ddrive Microsoft Windows Network



The autoexec.txt has



use c: c:\

use d: d:\

d:



if i then type vdos i get a new windows that shows



Z:\>use c: c:\

C => c:\



Z:\>use d: d:\

D => d:\



Z:\>d:



D:\>cd \pub

D:\PUB>use



Windows path

C: => c:\

D: => d:\

Z: => Reserved virtual bootdisk



D:\PUB>



If i go back to the cmd windows, cd to the new vdos directory vdos.v and run vdos using the same autoexec.txt i get



C:\>use c: c:\

C: is already assigned

C:\>use d: d:\

D: => \\ds2014\ddrive\

C:\>d:

D:\>cd \pub



D:\PUB>use



Windows path

C: => \\ds2014\ddrive\PUB\vdos.v\

D: => \\ds2014\ddrive\



D:\PUB>



As you can see c: is assigned to the current directory i.e. the "start in" directory and there is now no way to re-assign it

[Jos]

The mandatory Z: ‘boot’ drive indicates an early vDos version, 2014 or so.

Read the FAQs page of vdos.info! Mapping a Windows drive letter, then assigning that to a vDos drive letter is an option, but no sensible one.

Eventually wipe out autoexec.txt and enter the USE commands by hand. “C: is already assigned” just means you already did an “USE C: whatever” in that vDos instance, or you have files opened of that vDos C: drive.

Jos