gmax won't start up after the initial time. The messages I am getting indicate that it has become case sensitive with respect to names. The installer put in a directory named 'stdplugs' but the program wanted it to be 'StdPlugs'. So I renamed it. It still says these libraries fail to initialize. I must be missing a windows module but I did put in the recommended winetricks things, and now, I am stuck. Any ideas?
On 07/16/2010 06:04 AM, A Nonny Moose wrote:> gmax won't start up after the initial time. The messages I am getting indicate that it has become case sensitive with respect to names. The installer put in a directory named 'stdplugs' but the program wanted it to be 'StdPlugs'. So I renamed it. It still says these libraries fail to initialize. I must be missing a windows module but I did put in the recommended winetricks things, and now, I am stuck. Any ideas?Hi, WINE will read in additional DLL files that you specify manually on the command line. Use the WINEDLLOVERRIDES environment variable, placed before your launch command, following the syntax specified in the manual: http://ftp.winehq.org/pub/wine/docs/en/wineusr-guide.html#AEN586 The actual library files should preferably be in the directory from which you are entering the launch command. In these cases, I cd to the actual "Program Files" directory inside the WINE bottle, copy the DLL's there, and always launch the program from there. I've found that character case in DLL filenames was irrelevent when loaded in this way, but your mileage may vary. Bryan
A Nonny Moose wrote:> gmax won't start up after the initial time.Terminal output? Wine version?
A Nonny Moose wrote:> Only if I am desperate. I generally run from the GUI. >A Nonny: When a program is run from the terminal, Wine generates error messages and other information that the project might find useful to help solve this problem. Can you please also create a bug report so the project can track progress on solving this issue? Thank you. James McKenzie
Thanks for the kind words. I'll spend more time with the documentation and take your advice. I do have an account on Bugzilla (two in fact, by accident), and I am on the AppDB as well. Further investigation with gmax will not happen until about Wednesday of this week as I have other fish to fry. Again, thanks for the tuition.
Thanks, Bryan. I am a little rusty on scripts, so that is very useful. I haven't done any serious console work since 1980. Shows how interest waxes and wanes,eh?
Thanks, Bryan. I'll bet there was a time when we could have made beautiful scripts together. I learned UNIX when I was working on staff at the University of Waterloo for a couple of years. I needed a break. This was in 1980, and when I left, I went back to sales support on main frames, so there wasn't much scripting there. When I started out, the Byte hadn't been invented by the It Beats Me company. That happened the year we were evaluating the first main frame for the bank I was working for at the time. The I've Been Moved company interfered with the board of directors and got a year's delay so they could announce the /360, but it didn't do any good. We now really needed the machine, and the /360 wasn't deliverable at the time of the announcement. We went with NCR because they had a lot of American banks already and had drivers we needed for the cheque sorters. So, I go back a long, long way. Microcomputers? What? You've got to be kidding. [Laughing]
I have a very chequered career. I thought I wanted to be a chemical engineer, but was saved when there was a steel strike one summer and my job disappeared so I couldn't make my fees and expenses. So in the summer of 1959 I went to work for a chartered bank as a "supernumerary", a.k.a. gofer. I learned a lot in about six months, and wound up being transferred to the big T.O. as a teller. I got to be head teller, then assistant accountant. I sent in a flow chart of a system I devised to operate the branch posting machine to post something that had just come out, and for which there were no instructions. Working with the ledger keepers and the proof teller, we got the thing working, so I documented it, and sent it in to the methods guys. Boom! I got transferred down town to the methods department. They seconded me to the EAM (you remember those, clunkety-clunk) section supervisor to work on acquisition of the bank's first major computer to do Demand Deposit Accounting (current accounts) for all the Toronto area branches. We had all the cheques, so all we had to do was capture the data, and have the branches report any other transactions. While we were waiting for proposals to come in from our short list of vendors (IBM, GE, NCR, Burroughs), I was assigned to assist the local printers to get their E13B cheque encoding right (yes, that's when it happened). So I did that, and since we had a sorter, did a program to test the cheques. By then, I was a self-taught programmer in assembler. That's when the International Brotherhood of Magicians got in the act with the board of directors, so we got to cool our heels for another year, getting ready to convert all the EAM applications to the new machine. We had a room full of clankers, three operators, and a supervisor who were being obstinate. We persevered. So the bank got an NCR 315 that had 10,000 (no fooling) words of 12-bit decimal addressed memory, some Card Random Access Units, a line printer, a paper tape reader, an English Electric Card shuffler (I mean reader), and two 16-pocket cheque sorters. The machine did arithmetic in decimal. In those days, mucho dinero. About this time, since I was the only programmer, I collapsed. When I got back to work, I had this nice staff of 14 novices who knew only a little less than I did. We got the applications running anyway. Remember, in those days if a university had a computer at all, it was a curiosity in the EE lab. After a few years the bank had a political falling out with NCR and decided to go Honeywell. I liked neither the Honeywell machine (a fancier 1401) nor the attitude of its people, so I found a job with GE's Information Systems and Defence Products Department. We sold main frames, jet engines, radar, rockets, and other things that are probably still classified. I was attached to the Toronto data centre as a support programmer and sales support analyst. That's when I got my first taste of Multics. We actually sold a few of them to various classified outfits, and one to Bell Canada. We also sold smaller stuff, like the 600 line (72-bit words), the 400 line (24-bit words) and the 200 line (18-bit words). Byte? Wazzat? Well, I did some career searching and wound up back with the GE group, now part of Honeywell. At the time we figured they would soon be merged with Fairchild Semiconductor and the new company would be called Fairwell Honeychild. Anyway, Honeywell stuggled along for a while by making their best salesman into the general director with the usual results. "Apparently the rot had set in worldwide because one day we found that we had been bought by CII-Honeywell-Bull (a.k.a. Charles de Gaulle and Co.). After a few years of doldrums, Bull decided that main frames were not for them. After a failed experiment with Zenith, the folded the large scale side of the business and let all 8,000 of us go in one day world-wide. After I got over the shock that, in fact, the big computer business was as dead as a dodo (1990), I became a professor of computer science in a local college, working part time until I retired at age 65. I'll be 73 in September. So here I am playing catch up with the baby boomers just for fun and something to do.
So I am two score older than you. All that means is that I am less patient and more subtle. Long experience just makes looking back more fun. Where I come from, by the way, a generation is thirty years. You GenX, Y and Z types move too fast for me. Anyway, good morning. It's my grocery shopping day, so I'll be out most of the day. I have a ton of research to do on this, so I probably won't post until I finid something interesting. TTFN. John.
Plus ?a change, plus c'est la m?me chose. The French say it better.
I am afraid that my interest in getting gmax functional has waned for the moment. I got tired of bashing my brains against several things at once and decided to slay the dragon one head at a time. Of course you know what when you cut off a head, two more grow in its place. *sigh*. I hear that you can slay one of these things by burying it in horse manure. Or maybe that only works with Dr. No.
A Nonny Moose wrote:> I am afraid that my interest in getting gmax functional has waned for the moment. I got tired of bashing my brains against several things at once and decided to slay the dragon one head at a time. Of course you know what when you cut off a head, two more grow in its place. *sigh*. > > I hear that you can slay one of these things by burying it in horse manure. Or maybe that only works with Dr. No. > >ah, the old Hydra. Yes, once you fix one problem, two more come up to replace it. Not nice, but a real rule of computing. Yes, it does pay to step back and look at the entire problem, rather than concentrate on one particular facet of it. BTW, is there an Applications Database entry for this program? If not, could you take some time to create one and give the program a rating? James McKenzie
I think so, but I'll have a look tomorrow. Not seeing straight tonight.
Is this a wine bug or a gmax bug? It has been so long since I ran gmax on windows that I don't really know any more. I also have a hard time reading between the lines on these console reports. I just ignore the fixme: things as known problems, but never know what I am really looking at with an err: I assume I can cause the fixme's to go away by turning them off using the debug variable. Just too much bother. I am slowly getting wise to the nomenclature, but it is trial and error for me at the moment. I hope you haven't done anything serious to your neck. Maybe you just sat in a draft too long or slept with your head at a funny angle. Good luck on that. I have had diagnosed rheumatoid arthritis since about 1985 and living with a thing like this is a pain (literally, at times).