-
Following the instructions, not connecting from the Prodigy client. This is what appears in the terminal that I used to launch DOSBox.
|
Beta Was this translation helpful? Give feedback.
Replies: 16 comments
-
Thanks for reporting. The instructions were written using Docker on a Mac running MacOS 13.1 and are not exactly right for Ubuntu. It looks like you must have corrected the I did run through testing on Ubuntu 22.04 and the big takeaway is that the dosbox-staging snap package uses AppArmor, but the configuration has not been updated to permit dosbox-staging network access. Your log message I don't know enough about AppArmor to craft a configuration to permit network access, so I instead downloaded a binary distribution directly from here and installed the dependencies as follows:
Then, running the dosbox-staging binary distribution, I was able to connect to the Prodigy server running under Docker. Let me know if that doesn't work, and I'll dig deeper. |
Beta Was this translation helpful? Give feedback.
-
Also, you'll need dosbox-staging 0.79.0 or newer. (0.79.0 introduced the |
Beta Was this translation helpful? Give feedback.
-
I updated to Ubuntu 22.04 so I could get Docker Desktop.
|
Beta Was this translation helpful? Give feedback.
-
Can you share the output from the prodigy-server container? |
Beta Was this translation helpful? Give feedback.
-
I also tried it on macOS 10.15 Catalina on a i9 Intel macintosh.
|
Beta Was this translation helpful? Give feedback.
-
From Ubuntu. I see something about a user table not being there? Should I reinstall from scratch?
|
Beta Was this translation helpful? Give feedback.
-
prodigy-server from Macintosh, with error 'API 18' in client
|
Beta Was this translation helpful? Give feedback.
-
Ok, after you start the server, you must run the database migrations and load the objects: Try these commands from the same directory containing the
|
Beta Was this translation helpful? Give feedback.
-
Ubuntu 22.04 I wiped out the docker end and reinstalled. I'm past the 'CM 4', I'm now getting the 'API 18' error on Ubuntu and macOS Catalina.
|
Beta Was this translation helpful? Give feedback.
-
First, the reason for the majority of the stack trace is #35 This bug aside, the server appears to be operating normally now, though clearly returning something that the Reception System doesn't like - causing the API 18. Sadly, the documentation I have only covers API error up to and including 17. You're using the RS version downloaded from archive.org? If you run |
Beta Was this translation helpful? Give feedback.
-
I clicked on 'and the disk image is here' in the delivery-system README.md
|
Beta Was this translation helpful? Give feedback.
-
Ok that looks totally right.I’m not quite sure why you’re getting this error as this exact set of software and objects is working for me. Nevertheless, I’ll work on a fix for the issue i mentioned and add some better diagnostic logging.
|
Beta Was this translation helpful? Give feedback.
-
Another data point. I went to winworldpc to get their Prodigy 2.1 client and did an install of it in my Ubuntu DOSBox and it is working.
|
Beta Was this translation helpful? Give feedback.
-
I suspect this may have something to do with the fact that the 6.03.17 version was the IBM User's Club and executes some different logon programs, by default. When I tried this, the client did produce an API 18 (but oddly did not send the message causing the stack trace). I resolved it as follows: If you go through the setup, choose network "Q", then exit at the logon screen, you can then change Replace:
with:
6.03.10 does work too, and should receive any newer objects from the server, but the executable itself may lack some fixes found in 6.03.17. Only time will tell. |
Beta Was this translation helpful? Give feedback.
-
Since this is not a problem that can be resolved within the server code, I'm going to migrate it to a discussion. We can continue there. |
Beta Was this translation helpful? Give feedback.
-
More deeply, the problem is that the IBM User's Club is what prodigy called a "Closed User Group". Such groups had a two character abbreviation ( Right now, the code is only targeting "Prodigy" users, for lack of a corpus of data for other user groups. Thus, the code returns "TL" as the user group identifier in the logon response. I suspect that one of the programs executed on logon with the 6.03.17 client using the default object ( |
Beta Was this translation helpful? Give feedback.
Another data point. I went to winworldpc to get their Prodigy 2.1 client and did an install of it in my Ubuntu DOSBox and it is working.