Perl_Tcurpad Error

[Fynmun]

This might or might not be a unique problem.

The Scenario: I'm setting up a very small server (mainly for testing, etc) that is run on a laptop. I've already got one server up and running on a full tower, so setup was not a problem.

Result: First error was cured easily. Installed Perl 5.10 not 5.8. (It had popped a missing file message, perl58.dll.) That out of the way, reboot, and try again. Second and the most persistent error. The full error message is this:

"The procedure entry point Perl_Tcurpad_ptr could not be located in the dynamic link library perl58.dll."

Nothing more, nothing less. On my 'main' server, this error never has popped up.

Any suggestions/cures would be great.

Thanks,

Fynmun

[Apoc0]

are you still using 5.10 and also is it 32bit or 64bit?

[Fynmun]

Uninstalled 5.10 and installed 5.8.

The laptop is 32bit x86 (my tower, strangely enough, is 64bit and no problems at all).

A friend of mine said it might've been the .dll files I may have missed, but I checked and they're there. I'm halfway tempted to uninstall everything and start from scratch.

[Fynmun]

UPDATE: I uninstalled everything regarding the server (down to the SQL database editor) and reinstalled everything, following the guide step-by-step and double checking everything. Also installed the client (EQ Titanium). Error message is still there. Maybe it's the computer?

[Apoc0]

Hmm, ok check your environment variables, under computer properties. Make sure you have all thats needed under that PATH variable. For example i have PHP, PERL, MySQL, and Apache.

[Fynmun]

I wouldn't have thought to look there...

Checked it. The needed ones (PERL & MySQL) are there. Compared to the other server while in there and ended up adding a few. A couple restarts later, no good.

From the error message it seems like it can't find something in the actual .dll file, which in my mind would imply the file's corrupt. But what's the probability of getting 2 corrupt files in a row (unless the perl58.dll is just bad on download to begin with...)? I'll check out the .dll and see if maybe the install I got was bad.