I have Win 98SE try unzipping with WINRAR instead of winzip it works great! (I found that winzip messes around with the folders i.e. deleats them, moves them ect.)I don’t know if this will help but all the scripts work great on my box.
sirquadalot,
I’m on a Win2k machine and have WinRAR so tried it to uncompress 1.5. Still the same problem with TM, so I don’t think it is the decompression tool. Another thing I found out though. Not only is the TM-PANELrevE.ZBR corrupt, but also the Temp.ZMT and blRhino.ZTL files. When I copied the versions stored in my ZB1.23b folder over into the ZB1.51 folder everything worked fine.
- Bob
Having successfully downloaded, I unzipped all the files (using WinZIP with the Use Folder Names box checked) into a new branch starting from C:\Program Files\ZBrush\ retaining exactly the same directory structure as in the zip file.
When I first tried the new version of Texture Master that came with version 1.5 it instantly died on loading: program has attempted to perform an illegal action… good night! BUT the good news is that I seem to have found a consistent pattern here.
When I reloaded 1.5 and tried again (several times) it worked perfectly and consistently (no messing around changing folders or anything else). Haven’t had time to try all the new scripts, but then loaded the new InBetweener, which also ran OK. Reloading Texture Master either by the Previous button (nice touch!) or the Load button still resulted in a working copy of the script. And still works OK after creating several new ZSphere tools.
The only way I’ve found so far to replicate the initial problem with Texture Master is to do what I did the first time: load 1.5, FIRST run the New Features tutorial script, THEN draw a sphere and run TM. At this point it invariably crashes.
It therefore looks like it’s something about the New Features script itself, or more likely something about the state in which it leaves the environment, that makes TM unwilling to be next in line… over to you Aurick.
EDITED: Forgot to mention - no problem with corrupt files unlike the last couple of posts. Sounds like that might have been some corruption during the download maybe?
I just wanted to say that I am having this and various other script problems. Thx
:ex: UPDATE:
My crashing due to loading zscripts was solved by placing the default directory ‘ZBrush OneFive’ in my ‘[bootdrive]:\Program Files’ directory. I had placed ‘ZBrush OneFive’ inside of a ‘ZBrush 1.5’ directory. Now I never crash to desktop.
I still have the problem with the 1.5 TextureMaster Show and Tell.
I tried what ub52 has wrote earlier and that solved my problem with TextureMaster 1.5. 
The 123b version of TextureMaster works up to Ch. 5. Then there’s a tool missing. :ex:
I’ve was having this problem with TM, but then on a whim I downloaded 1.51 again and re-installed. Workes fine now. Also worth noting that there was a definite size diference(maybe .5mb) between the first zip I had downloaded right after release and the one I downloaded yesterday. They were both 1.51P. Was there an update that I was unaware of? Anyway, that worked for me, maybe it will for you too.
I also just redownloaded and reinstalled. My new download was also bigger.
No more crashing with Texture Master.
Thanks for the tip, Mad Jack 
Me too. I started having the crash mentioned by another user, where trying to advance through the materials in a Material Pack causes the crash to desktop, so I rebooted, downloaded 1.5 again and overwrote the original files.
The TM Show and Tell runs perfectly all the way through, but any Material Pack still crashes. When I first set up my custom default script and the Material packs, they worked perfectly, and I was able to scroll through them without a problem. But last night I started having crashes in the Material Packs.
I can’t get TM Show and Tell to function at all. Crash boom.
>>EDIT<< Never mind :eek: I followed others’ advice, redownloaded it again, and TM Show and tell works fine now!
Also make sure that there are no “.” in the names of your folders in ZBrush. This will mess up scripts.
Thanks to Jaycephus for pointing this out.
Edit: In another thread, 
<font color="#949494" size=“1”> November 05, 2002 Message edited by: gummie </font>