32 or 64 bit?

[Anonymous]

Is there a way through maxScript to determine if a user is running the 32 or 64 bit version of Max? I need to use this information to point the user to the correct plugin folder when we install our custom tools.

[DarrenP]

does he have a 64 bit os?

[Anonymous]

Yeah.

[Steve_Curley]

getMAXIniFile()
Returns the full path to the .ini - which includes either "9 - 32bit" or "9 - 64bit" (in the case of Max9), "2008 - 32bit" and "2008 - 64bit" for Max2008. A quick string search should find that for you.

[Anonymous]

Sounds like that'll work. Thanks.

[Anonymous]

Or just use is64bitApplication() (see "64 Bit Values - Double, Integer64, IntegerPtr").

[Anonymous]

That's exactly what I was looking for, thanks.

[Anonymous]

That's exactly what I was looking for, thanks.

Since the method was introduced in Max 9, to ensure the script works in Max 8 and earlier, you should either call it inside a try()catch() or check the Max version first and if it is less than 9000, assume 32 bit version without calling the method.

[Anonymous]

...or check the Max version first...

Hi Bobo!

What is the code for this?

Thanks.

Sascha

[Steve_Curley]

maxVersion()

[Anonymous]

Geeesh...

...lucky one able to read...

..got tomato on my eyes...

Thanks man!

Sascha

[Anonymous]

Works fine, thanks.

Now I try to delete a folder with white space name, e.g. "C:\a test\".

This code works fine:

doscommand "rmdir \"C:\a test\""

0 is returned, the folder is gone.

...but I have to build the commandstring via script, so this doesn´t work:

myPath = "C:\\a test\\"
myString = "rmdir" + " \\" + "\"" + myPath + "\""
doscommand myString

161 is returned and the folder is still there...

Any ideas?

Thanks and best regards.

Sascha

[Steve_Curley]

You need to look more closely at what you're producing there. Look at it section by section.

The MyPath does not need the trailing \\

MyPath = "c:\\a test"

The MyString does not need the first " \\"

MyString = "rmdir" + " \"" + MyPath + "\""

Which results in

rmdir "c:\a test"

But your code was producing

rmdir \c:\a test\

which was trying to find a directory called "c:" in the root of the current drive (containing a directory called "a test"), which obviously doesn't exist, hence the error.

[Anonymous]

Thanks Steve, that works!

But what I don´t understand is:

myPath = "C:\\a test\\"
myString = "rmdir" + " \\" + "\"" + myPath + "\""
doscommand myString

When I print myString it returns

"rmdir \"C:\a test\""

not

rmdir \c:\a test\ 

as you mentioned...

So where are the colons gone?

Nevertheless - thank you very much!

Sascha

[Steve_Curley]

There's only 1 colon - immediately following the C as in "C:"

If you open a command prompt and type
<code>
rmdir "c:\a test"
</code>
it works. Consequently you must recreate exactly that sequence of characters - no leading or trailing backslashes, which you keep putting in there. They are not only not required but they are causing a different (and incorrect) path to be passed to rmdir.
Your code will put the backslash before the C - because you're putting it there. It puts a trainling backslash in as well - which is not required.

Also, whenever Maxscript prints a string - it puts quotes around it for display only - they are not part of the string being displayed. I left them off above to try and simplify things for you.
Look at the attached image - every string displayed (in the bottom section) has quotes around it, but they are clearly not part of the string itself.

[Anonymous]

Also, whenever Maxscript prints a string - it puts quotes around it for display only

Yeah, thought this might be the case. Now I know!

Steve, again thank you very much. Works very well!

Now I could finish to script a *.mzp installer package for my scripts AND a script to uninstall the whole thing again. Very comfortable.

Best regards.

Sascha