I got windows working in the files both in his repo and the post I made.
My alterations may have caused the code modification necessary for lextab and yacctab (wouldn't surprise me).
Win32 was a total Pita!!! to get sorted out.
I'm not thrilled my work was released either, but since it was, no sense keeping them from my updated work. Thus the post after the repo post made by swgmasters.
Glad to see it wasn't my imagination about PLY. I was pretty sure it was a necessary add-on, but no one would validate it.
If you have any useful / insightful information for these guys/gals it would be appreciated.
Appreciate the effort yourself and the original group put into this. :0)
That's good work, it was frustrating that the server would barf on loading on windows for us. Since the ubuntu version was working well enough it was decided to continue with it and return to the Windows version down the road. As I'm sure you are well aware, working with this beast is daunting and can be soul crushing.
No problem confirming the PLY usage. I haven't looked into the difference to see why those two files would now be needed, but I might take a gander later.
The most useful advice I can give is don't give up... god there were so many times when a brick wall was hit and it seemed like we were missing some vital data file that would prevent the whole thing from working. Refusing to give up is what saved things back then. In the case of the missing appearance data, some debugging showed that the server was looking for "APPR" chunks. A quick grep of dsrc showed that none of these files had these chunks. So I turned to the client files, and it turns out in .lod, .msh, and .cmp files had "APPR" chunks in them. I wrote a quick script to pull just these chunks out (because just using the raw client files would be too easy) and magically this worked. Anyway, that's just an example of not giving up.
The other advice I would give is about oracle:
1) Start with a clean windows os (screw linux installs of oracle, it's really a black art... but if you must USE ORACLE LINUX)
2) Install it with the option to create a database and uncheck "Create as Container database"
3) Remember what the "Global database name" is (and naturally the password)
Other than this, all the default options can be selected when installing oracle on windows. If installing oracle on the same windows installation as the dev environment then importing the database is just a matter of having perl installed and running a single command (copied from Mr. Rogers post a couple pages back):
database_update.pl --username=system --password=yourpassword --service=yourdatabasename --goldusername=system --loginusername=system --createnewcluster --packages
For new people getting on, getting this part of things set up seems to be the hardest part. So, make life simple and use windows.