A client recently reported that upon upgrading to W7, a feature available in XP & below no longer works. Can anyone confirm this, as I do not have Vista or W7:If the logged on user has a drive mapped or assigned either via a SUBST command or a NET USE; eg: SUBST A: C:\A-DRIVE or NET USE A: <sharename> or similar; the purpose of which is to make the local PC "think" it has a writeable A: drive; then in XP and below if you ran a cmd prompt or had an application that issued a command line execution; it would inherit those settings. That is, the command being executed would 'know' about the A: 'drive'.My understanding was that in XP and below, the 'virtual' 386 enviroment created was always a duplicate of the 'MSDOS' "environment" that existed just prior to Windows loading on boot. Which was why such commands as SUBST if placed in the system's AUOTEXEC.BAT would then be available to that PC and all users, and shelled command prompts.My client [who is very technical and generally proficient] is telling me this is no longer true with W7 [and also apparently with Vista]. Is this correct?Is there a workaround, as otherwise this will require a re-write of this portion of my application [which I would prefer not to do!].Can anyone shed some light on this please?Thank you.David

It was time for you to re-write it anyways. However the subst example you've give does work. Haven't use the net use command to verify. I don't have a floppy drive in my laptop and after the subst, it now shows A: drive as a hard drive and subst from the command line shows A: as a virtual drive to C:\A_Drive. However I'm not able to confirm if there is a problem is the floppy drive A exists, would it redirect to C:\A_Drive MCSE, MCSA, MCDST [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]

Hi,I was wondering if the portion are 16-bit. If so, this 16-bit has been cut off in windows 7. At this point, I would suggest using a emulator DOSbox in windows 7 as a workaround. For more information, refer to http://sourceforge.net/blog/potm-200905/.