IB Joe wrote to All <=-
I don't work in the Tech industry, my expertise lays outside of there.
I bought a micro computer the other day to host the BBS on it and for
the life of me I could NOT install a 32Bit version of windows 10 on
it... There was 4 failed attempts. I went with the 64Bit version and installed the hack DLL file that will let me run 16Bit doors.
Is there something I don't know about todays hardware that it would
reject a 32Bit OS??
I copied the BBS over to the new micro-server and it's complaining about the file needed SSL/SSH cryptlib is missing... Why can't a cut and
paste work smoothly. The latest version of mystic was released just the
IB Joe wrote to All <=-
I don't work in the Tech industry, my expertise lays outside of there I bought a micro computer the other day to host the BBS on it and for the life of me I could NOT install a 32Bit version of windows 10 on it... There was 4 failed attempts. I went with the 64Bit version and installed the hack DLL file that will let me run 16Bit doors.
I've never heard of issues with 32-bit OSes on modern hardware. I'm running Windows 10/32 bit on my BBS, but I was running it on a 32-bit
CPU, and now in a virtual machine.
Is there something I don't know about todays hardware that it would reject a 32Bit OS??
The only issues I've read about are on 64-bit systems with over 4GB of
RAM installed.
I copied the BBS over to the new micro-server and it's complaining ab the file needed SSL/SSH cryptlib is missing... Why can't a cut and paste work smoothly. The latest version of mystic was released just
If you are switching between 32-bit and 64-bit then you'd need to
replace the corresponding .dll files with their 32-bit or 64-bit
versions.
It is saying you don't have Cryptlib so that means you'd need to have cl64.dll in your Mystic directory for the 64-bit version of Mystic (or cl32.dll for Mystic 32-bit).
Normally the installation program puts the proper .dll file there for
you, but when you switch you need to do it yourself.
If you have an unarchive copy of Mystic in a temp folder you can do "install extract cl64.dll c:\mystic" and it will extract cl64.dll to c:\mystic for you and that might clear up your message.
... User Error: Replace user and hit any key to continue...
Is there something I don't know about todays hardware that it would
reject a 32Bit OS??
I just copied it over and it started giving me grief about the SSH/SSL thing. I downloaded the latest version of mystic and updated the
cl64.dll and it's still giving me static...
I just copied it over and it started giving me grief about the SSH/SS thing. I downloaded the latest version of mystic and updated the cl64.dll and it's still giving me static...
The instructions mention this too, but I don't remember if its still relevant:
In addition to the .DLL file, Cryptlib may have a dependency on the
Visual C++ runtime which may or may not need to be installed on your particular system. This depends on how the .DLL files themselves were compiled. If you have the appropriate .DLL file in the root Mystic BBS directory but you still get a message on server startup that says
Cryptlib is not installed, then you likely need to install a Microsoft runtime that is required by Cryptlib (for example):
https://www.microsoft.com/en-us/download/details.aspx?id=48145
This fixed the problem...
| Sysop: | Gate Keeper |
|---|---|
| Location: | Shelby, NC |
| Users: | 764 |
| Nodes: | 20 (0 / 20) |
| Uptime: | 39:50:43 |
| Calls: | 11,275 |
| Calls today: | 1 |
| Files: | 5,288 |
| D/L today: |
80 files (9,985K bytes) |
| Messages: | 521,283 |