Is using both 8th and 9th versions possible?

[akalenuk]

I tried to install both versions on two different drives, but it seem thay use the same libraries from C drive. I'm not very sure, but it seems so, because i could not repeat that lzLeft bug i was talking about. Should i setup something manually, or this is just a mirage?

[Casper]

If there are any references to masm32 in your environment, remove them and reboot your computer.

Casper

[P1]

I keep all my old versions.

MASM32.v8
MASM32.v7
MASM32.v6

When I want to use it, I rename the current one to MASM32.v9 and the one I want to use to MASM32. 

But I do not use both at once.

Regards,  P1  :8)

[hutch--]

There is a very simple method to do this, install each version on a different partition as all installs are designed to do this. I still wonder as to the virtue of doing so when the later version encloses the earlier versions and is a lot more powerful.

With the parsing issue using the szleft and szRight library procedures, if you explain what you are parsing, it should be easy enough to apply a solution for you and with the later macro suport, it should be a lot more clear code.

[akalenuk]

There is a very simple method to do this, install each version on a different partition as all installs are designed to do this.

And so i did. 8th is on "C:" and 9th on "E:".

I still wonder as to the virtue of doing so when the later version encloses the earlier versions and is a lot more powerful.

I was not going to install back 8th until that bug shown off. And as soon as the code is written and forgoten, i would no more keep any old versions.

With the parsing issue using the szleft and szRight library procedures, if you explain what you are parsing, it should be easy enough to apply a solution for you and with the later macro suport, it should be a lot more clear code.

No need actually. I was pasrsing script for a 3D engine in order to multiply some object. Most of the time i'm bound to write C code for thin engine, but if it comes to external tools, i usually take MASM32. Just to have some fun at work. Thus clear code or high level syntaxis is not the really the features i want :bg

[akalenuk]

I keep all my old versions.

MASM32.v8
MASM32.v7
MASM32.v6

When I want to use it, I rename the current one to MASM32.v9 and the one I want to use to MASM32. 

I see. So the path would be the same for all versions. Interesting.

[P1]

I see. So the path would be the same for all versions. Interesting.

The major benefit is code written for a lesser version does not have to be re-written for the new one, with drive/path changes.

Always use the Captain Kirk Method, always leave yourself a way to go back or escape.

Regards,  P1  :8)

[KSS]

I use SubSt to assign a drive letter to folder-path (with MASM32 folder that I need at this moment). In this way I have clear root folder on my drives. And not modify file system (while rename folder)

For help: Open command.com and type "SubSt /?"