|
-
Nov 8th, 2000, 09:42 AM
#1
Thread Starter
Hyperactive Member
Hi,
Help! My Visual Basic installation went in the trash today and when I reinstalled it, I could no longer use long path names. I compiled a project and ran it from another machine and it worked fine there.
If I change the path to the DOS short path, it works fine.
I just reinstalled Service Pack 6 on NT and that did not help. I'll try and reinstall VS Service Pack 3 now. The only thing I can think of I did recently was installed Visual Studio Installer 1.1 or 1.2 (I don't remember).
Has anyone experienced this? Can anyone help?
Last thing to do is wipe my C drive and reinstall NT.
Thanks,
JazzBass
JazzBass
In the .NET era
Trying to remember VB6
Progress: 
XP Professional @ Home
and @ the Office
-
Nov 8th, 2000, 10:28 AM
#2
Thread Starter
Hyperactive Member
Additional Info
Hi,
Just wanted to add that it looks like it's only with the SHELL command that I can't use long path names.
I tried using the DIR command, and it finds the directories without a problem.
Any help is appreciated.
JazzBass
JazzBass
In the .NET era
Trying to remember VB6
Progress: 
XP Professional @ Home
and @ the Office
-
Nov 8th, 2000, 11:12 AM
#3
Addicted Member
Have you used Chr$(34) to enclose the long path name? If not, try it and it is very effective.
-
Nov 8th, 2000, 12:06 PM
#4
Thread Starter
Hyperactive Member
Thanks Xmin
Thanks for the tip,
I've since uninstalled VB, so I really don't have a way to test it.
I've been kinda wanting to rebuild my system anyway, so I guess this is my chance.
The funny thing is that the same code, same everything works on other machines and not mine.
Go fig.
Thanks,
JazzBass
JazzBass
In the .NET era
Trying to remember VB6
Progress: 
XP Professional @ Home
and @ the Office
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|