Hi,
My final tests were running on a WinNT 4 box. I copied the nsmysql.so (renamed to
nsmysql.dll) file to the same directory as nscp.dll (c:/progra~1/aolserver/bin), and
in the config file, and I copied the entry for ${bindir}/nscp${ext} in
ns/server/${servername}/modules to ${bindir}/nsmysql${ext} in ns/db/drivers - The
nscp.dll module loads, but nsmysql.dll won't, still with the error 126 (file not
found)...
I then inversed the names of nscp.dll and nsmysql.dll files on the disk - From this
point, nsmysql.dll file loads, but gives an error about ns_dbDriverInit - this seems
normal, as it is a renamed console module, but the important point is that AOLServer
*can* find the file named nsmysql.dll - and that the system gives an error 126 on
loading the nscp.dll file, which is in reality the nsmysql driver.
This proves that AOLServer *can* find the nsmysql.dlI file, and from this, I can
deduct from this that there is a problem with the actual nsmysql module, and that the
Win32 error 126 in this case does not seem to mean "file not found".
The problem follows the *content* of the file, but not the *name* - unless it cannot
find a file that the module itself is dependant on... in which case, the error 126 is
not clear enough... and I do not have the Microsoft Dependancy Walker tool to hand to
check at this time...
Aggghhh!!!
- Daniel
---------------------------------
Nokia Game is on again.
Click here to join the new all media adventure before November 3rd.
