TBLPad is giving me the same error over and over again about COMDLG32.OCX

I have downloaded both runtime packs from shadowflares realm and to make the problem even worse
every time I run setup I get to the part where it tells me to click the button to start installing the runtime package,
then I look and the only button it has is exit setup, nothing else. Why can't this stupid runtime pack work
and why does TBLPad need that file so badly when its in system32 already?

-Get PyMS.
-Get a chill-pill.
-Try again.
-Try putting the file in the "system" folder.
-Try renaming the file to the proper name, extensions and all.
-Get PyMS.

Even thought TBLPad is more stable, PyMS's PyTBL is better documented in the program. Get the Windows version, since if you can't even set up TBLPad, you probably won't be able to set up Python.

Sorry for being a jackass. Oh well.

You know what, I didn't want to bitch about PyMS, but now I'm going to.

PyMS hasn't worked worth of shit for me, every fucking thing I do in that shit suite gives me an error.
Whether it can't save anything or it won't open shit, I get the same error. Tkinker can't do this,
Tkinker can't do that, FIX THE FUCKING THING AND I MIGHT USE IT.

I apologize to everyone that had to read that, but its the truth and now its told.

I must be a genius to get TBLPad and PyMS to both work, then.

Try setting up TBLPad from scratch.

EDIT:
I'm going to set up TBLPad right now. And then I'm going to tell you what I did. If something goes wrong, you're screwed.

You're an idiot. PyMS is in active development all the time and yet you don't report having problems? REPORT THE FUCKING ERROR MORON! You're probably doing something stupid, and even though I will help you I don't even see why I should since you're being such an asshole.

My experience with TBLPad, right now:

1) I download and extract TBLPad.Zip. I run TBLPad. "COMDLG32.OCX" error. Okay. Good.
2) I download and extract RunPack1.ZIP.
3) I go to my folder that I extract RunPack1.ZIP to.
4) I run Setup.EXE.
5) I click "OK".
6) I click the f*cking picture of the f*cking computer because I read the f*cking instructions that actually says "CLICK THE F*CKING PICTURE TO INSTALL".
7)TBLPad now works.

I put the expletives in 6) to denote importance. Read: "importance". Read: "6)".

EDIT:
F*ck my life twice as hard and make it twice as terrible as it is right now IF YOU STILL CANNOT SET UP TBLPAD.

EDIT2:
Oh, right, how f*cking silly of me. I wrote a "7)" when I really meant a "6)". Shoot me, it's all right. I already have no life, so there's no point in letting me to continue to exist. I'll just go over there and die now. Thanks, I love you. You're the best, Lord Malvanis.

EDIT3:
BASTARD. WHY HAVEN'T YOU ACKNOWLEDGED THIS POST YET.

EDIT4:
It's been 9 minutes. Do you know how long 9 minutes is? It's 3 minutes to the power of two, in other words, three minutes squared. And by now, it's probably been over 9 minutes. Why have you still not thanked me yet?

Post has been edited 2 time(s), last time on Apr 12 2009, 4:48 am by New-.Hydrolisk.

Alright. I've calmed down now.
Poiuy, I would have reported in the last few days but my life isn't revolved around this game or this computer,
I have had things to do and have barely been on it besides now to even say this, I understand PyMS is under development
and I shouldn't have been such an ass about it, but yes, whenever I save or do anything, even trying to close PyAI, I get an error about Tkinker or something about __call__ and some other things. I'm using version 1.2.0
As for Hydrolisk, I realize now that in my anger, I was ignorant and did not realize the computer was a button because in most installations I don't have to click a computer picture, My apologies to you.

Back to Poiuy, this is what I get on every program:

"Exception in Tkinter callback
Traceback: (Most recent call last):
File "Tkinter.pyc" line 1410, in __call__
File "Pydat.pyw" in line 3499, in save
File "Pydat.pyw" in line 487, in save
File "Pydat.pyw" in line 499, in saveas
File "Pydat.pyw" in line 490, in save
File "Libs\dat.pyc" in line 491, in compile
AttributeError: 'unicode' object has no attribute "write"

Replace pydat.pyw with whatever the program is, and thats pretty much same error every time. On PyAI, your program doesn't close unless Task Manager forces it to close by ending a process or forcing it by "End Program"
PyTBL gives same error when saving a .tbl file
Yeah, you get the idea.

By the way, Hydrolisk, I didn't respond in 9 minutes because I couldn't copy and paste that LONG ASS FUCKING ERROR.
PATIENCE IS GOLDEN, LEARN IT.

I never said your life revolved around the game or your computer, but if you don't even tell me the error, then you have no reason at all to say "FIX THE FUCKING THING AND I MIGHT USE IT.".

What operating system do you use? You are using the EXE version? What "things" have you tried to do and know don't work? Can I get the other errors you receive? The error you are showing can only show up when opening and possibly saving a file, but you said you have other problems, so I would like to have those errors.

OH HAI, I'M A FAGGOT AND A JACKASS.

(On a completely unrelated note...)

Lord Malvanis, please note that PyMS (source code version) requires the 2.5.x versions of Python, not the 3.x.x versions.

I'm trying to calm down and be nice here. I was angry, I got over it, thats in the past now.

PyTBL:
"Load Error: Unsupported TBL file 'C:/Users/bill/Desktop/Tools and Games/Game Utilities/Modding Tool Package/1. WinMPQ/rez/stat_txt.tbl', could possibly be corrupt"

PyDats error you can see from above.

PyAI had a closing error once but I have not recieved now when I tried it, I would give it to you but I didn't take the time
to record it when it happened before.

Since I have no reason to use the other programs (I'm not that serious of a modder yet) I can't tell you anything.
And I never said that you said my life revolved around this, I was simply explaining to you that I don't always have time to report things. Yes, I used the EXE version, PyTBL pretty much won't open it, PyDat doesn't save, and PyAI once had an error that wouldn't allow it to close using the X button, which I have not recieved a second time yet.

Can you please attach/pm me the stat_txt you tried to open?

Ew, ugly flaming topic.

Did it ever occur to you to google the name of the .ocx, download it and shove it up on System32?
I had this problem with Starforge around 6 years ago and I was already smart enough to use google

As to PyMS, it has never failed for me. I use the .exe versions so I didn't have to go through the hassle of installing python. And it sounds to me that your file is corrupted by that post. Did you extract it from patch_rt?

If you can't get TBLpad to work it's time to reconsider what you're doing with your life.

You could always just drop PyTBL and just use normal TBLpad that comes in the modding package from the DLDB. Then you wouldn't have to deal with active development software. Not that Pyms isn't good.

Edit: Unless of course you're already using TBLpad and you're just bitching about Pyms and I'm just confused. In which case good luck.

Exactly.

SUPER+R > RegSvr32 COMDLG32.OCX is your friend, OP.

I'd say this thread has gone on for long enough.

The conversation about PyMS can be taken to PMs or taken to a topic about PyMS. If you still have problems with TBLPad, feel free to post a new topic with a clear head.

And everyone else, especially you Hydro, if I see this shit again there will be hell.