MC Version 4.37 Workspace Issue

Has anyone had any troouble opening the *.dsw? I'm using VS C++ 6.0 and whenever I try to open the file, nothing happens. When I try opening the *.dsp file, I get a message saying "This makefile wasn't generated by Developer Studio." and doesn't load that way either. For the heck of it, I tried opening it with VS 2005 and it said the project files was corrupted. I've re-downloaded, but I can't make it work. Just me or has anyone else had these problems?

Thanks

I was able to open the workspace and build it find on VS Pro 6.0. I had to make my own workspace and projects to build it in VS Pro 2005, though.

Did you download and build it from the off this page:
http://www.gammon.com.au/forum/?id=8971

I just MD5 checker and isntead of the 576754efc0b70422b103a15d4dfcda03 sum for the file that post says, I'm getting ff90c8cc44b2b73ea744a71f67b1c081. I'm no expert with these things, but I was able to get the correct sum for v4.02 (which does build fine), so I'm less inclined to think I'm doing it wrong. I've gotten this sum on multiple downlods of the file.

Interestingly, I downloaded a few more versions - 4.12, 4.13 and 4.40. For 4.12 and 4.13, I get the right MD5 sum. For 4.40, like 4.37, I get incorrect ones. I did notice that these releases tgz's while the other ones on zip. Could that be a problem somehow?

I've had this issue too. My solution was to open the mushclient.dsw and mushclient.dsp files in an editor such as EditPadLite or SciTE and convert to Windows (CR+LF) line endings and save. For whatever reason, the files had Unix line endings which Windows can't read properly.

(For EditPadLite: Convert -> Windows (CR LF)
SciTE: Options -> Line End Characters -> CR + LF)

Yep, that fixed the project, thanks again.

I just logged onto the server which serves up these files and checked:



The figure given on the page quoted above is correct.

Make sure that Windows hasn't automatically unzipped the file for you, or some such thing (eg. turned it into md5sum mushclient_4.37_src.tar). Possibly the downloading process doesn't recognise the .tgz suffix and attempts to convert newlines to CR+LF in the .tgz file (which would be a mistake).