Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Invalid DOS Path
Message
From
21/09/2006 11:22:46
 
 
General information
Forum:
Visual FoxPro
Category:
Source Safe Control
Miscellaneous
Thread ID:
00667048
Message ID:
01156022
Views:
22
Only three years later (how time flies) I was confronted with the same problem, searched on the UT for a solution and - surprise surprise - I had a nice encounter with myself. However, the advice hereunder misses an important point. The two to be replaced strings are 260 bytes long and have trailing zero-bytes. Changing the path almost always requires enlarging or shortening the name. Removing zero-bytes is not really a problem, but entering them may be a hassle.

Christof Wollenhaupt has written a program (VSSProject.prg) that does this job automatically. It can be found here: http://www.foxpert.com/downloads.htm

Hope this additional info is appreciated.

>There's another possible cause of the "Invalid DOS path" message. Open the pjx (with USE) and look into the memofield SCCDATA of the first record. You'll probably see the outdated path somewhere between the many odd characters. Replace the outdated path by hand. Close the table and try again.
>
>
>
>>>My PC was upgraded to Windows 2000 Professional on Thursday.
>>>I used to have a C and D logical drives. My Working Folders for my Source Safe projects was on the D drive (the working folder was D:\work)
>>>
>>>Now I only have a C drive... and the Working Folder is C:\work
>>>
>>>When I tried to check out a project today... I changed the Working Folder from D:\work\tfi6785 to c:\work\tfi6785 (the files are on c:\work\tfi6785).
>>>
>>>I checked them out in Source Safe OK.
>>>
>>>When I went to Visual Foxpro 6.0 to open the project in c:\work\tfi6785, I get a new error message...
>>>
>>>"Invalid DOS path, d:\work\tfi6785".
>>>
>>>I went and checked out the Help File... but that information did not help me.
>>>
>>>I checked the c:\work\tfi6786\6785.pjx file... I opened it as a table and checked the first record in it...
>>>I looked at the sccdata field.. and it had the d:\work\tfi6785 path hardcoded in it in 3 places.... buried in binary data...
>>>
>>>So, what is wrong? Why did not Souce Safe change the SCCDATA field? And how do I fix it to point to the c:\work\tfi6785 folder?
>>>
>>>Thanks!!
>>
>>Tommy,
>>It happened to me too and I don't exactly remember how I fixed that. As far as I could remember :
>>Located users.txt in vss directory and got my ini file's path (it was users\cetin\ss.ini)
>>Opened the ss.ini under users\cetin and changed drive letters there.
>>Cetin
Groet,
Peter de Valença

Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
Previous
Reply
Map
View

Click here to load this message in the networking platform