[DUG] Windows 7 Network Oddity

John Bird johnkbird at paradise.net.nz
Thu Feb 17 18:52:53 NZDT 2011


How do you expand the path to UNC?

The reason I am surprised in a way that MS have done this is that using mapped drives added a layer of abstraction from the server – if a server had F: mapped to \\SERVER01\DATA  then the server could be replaced, the mapping moved to \\SERVER02\DATA  on the workstation in Windows Explorer, and the existing shortcuts and saved setups needed no change – in practice this is very convenient because it gave a very easy way to upgrade a server.  Also the network upgraders only needed to know to edit the drive mappings in Explorer, now they might need to go into software packages and alter settings for each.

I can cater for this in my settings, but it means that any time a server is replaced the settings will have to be edited, and the shortcuts will also will probably have to be edited, as usually the server name changes.

I already have to cater for this for network printers, eg a printer might move from being called HPLaserjet and changed from being mapped to \\SERVER01\HPLASER  changed to \\SERVER02\HPLASER  so in a sense its just more of the same (printers never had a mapping anyway).

John
 
I havent noticed it as I have always expanded the path to unc and beyond so that no matter what form they give me for the path,  it always evaluates to the same string.

Another thing that may effect you is that on 64 bit server using TS - constant crashes are being attributed to this issue.  And the workaround has been reported by other companies such as seagate - not to uses shared drives.  The error given is C0000006.


On 12/02/2011 12:20 a.m., John Bird wrote: 
?I have software used on networks that commonly uses its shared folder 
server as a mapped drive,  eg   M:\MyFolder with M: mapped to 
\\Server1\MySoftware\
If a program runs from there, started as M:\MyFolder\MyProgram.exe  , there 
is a difference between XP and Windows 7:

XP   Application.exename   returns    M:\MyFolder\MyProgram.exe

Windows 7   Application.exename   returns 
\\Server1\MySoftware\MyFolder\MyProgram.exe

ie Windows 7 expands the mapped drive to its real UNC name rather than 
returning the mapped drive name, even though the program was run from a 
shortcut using the mapped drive name.

Anyone know if this is a setting or preference that can be altered?   Or do 
I have to live with either being returned depending on Windows version?

Others may wish to check if this has ramifications for them!

John 


_______________________________________________
NZ Borland Developers Group - Delphi mailing list
Post: delphi at delphi.org.nz
Admin: http://delphi.org.nz/mailman/listinfo/delphi
Unsubscribe: send an email to delphi-request at delphi.org.nz with Subject: unsubscribe

__________ Information from ESET NOD32 Antivirus, version of virus signature database 5863 (20110210) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com



-- 
Regards

Rohit Gupta
B.E. Elec., M.E., Mem IEEE, Mem IET
Technical Director
Computer Fanatics Ltd

Tel 4892280 
Fax 4892290 
Web www.cfl.co.nz

--------------------------------------------------------------------------------
This email and any attachments contain information, which is confidential and may be subject to legal privilege and copyright. If you are not the intended recipient, you must not use, distribute or copy this email or attachments. If you have received this in error, please notify us immediately by return email and then delete this email and any attachments.


--------------------------------------------------------------------------------
_______________________________________________
NZ Borland Developers Group - Delphi mailing list
Post: delphi at delphi.org.nz
Admin: http://delphi.org.nz/mailman/listinfo/delphi
Unsubscribe: send an email to delphi-request at delphi.org.nz with Subject: unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listserver.123.net.nz/pipermail/delphi/attachments/20110217/5a4f2881/attachment.html 


More information about the Delphi mailing list