RobertLM78 Posted June 5, 2014 Share Posted June 5, 2014 Hello there 99ers! I thought I should start a new thread about this: Roadrunner had posted an issue with this cart using Classic99, however, trying Robotron on MESS, I found that loading the cart completely crashes the entire host system (a nasty lock-up - I can't even go to a virtual console to kill the MESS process). Roadrunner reports it working for a time in Classic99 before it crashes (I presume crashing Classic99). Regardless, it appears something isn't right with the .bin file. Quote Link to comment Share on other sites More sharing options...
Retrospect Posted June 5, 2014 Share Posted June 5, 2014 (edited) Hello there 99ers! I thought I should start a new thread about this: Roadrunner had posted an issue with this cart using Classic99, however, trying Robotron on MESS, I found that loading the cart completely crashes the entire host system (a nasty lock-up - I can't even go to a virtual console to kill the MESS process). Roadrunner reports it working for a time in Classic99 before it crashes (I presume crashing Classic99). Regardless, it appears something isn't right with the .bin file. These .BIN files - were they originally disk images that were converted to cartridge? Usually when they boot you would see the writing "Cart conversion by Tursi" for a second before it boots. (it comes up whenever anyone has used the converter utility from tursi, unless they used a different utility) Just wondered if they are a bad conversion, as I have produced some bad ones of my own? Edited June 5, 2014 by Retrospect 1 Quote Link to comment Share on other sites More sharing options...
RobertLM78 Posted June 5, 2014 Author Share Posted June 5, 2014 Honestly, I'm not sure how .BIN files are made. I've seen the "Cart conversion by Tursi" before, but figured it was for the specific cart (DM 2000). If it is just a bad conversion, we should fix that, because it's affecting at least 2 emulators, and probably more I'd figure. Quote Link to comment Share on other sites More sharing options...
Asmusr Posted June 5, 2014 Share Posted June 5, 2014 This version works fine for me. It is a zipped MESS (rpk) file. as_robotron_2084.zip Quote Link to comment Share on other sites More sharing options...
+mizapf Posted June 5, 2014 Share Posted June 5, 2014 trying Robotron on MESS, I found that loading the cart completely crashes the entire host system (a nasty lock-up - I can't even go to a virtual console to kill the MESS process). This kind of crash should not happen. What have you done to make it crash? Can you upload the cartridge? What MESS version are you using? Quote Link to comment Share on other sites More sharing options...
RobertLM78 Posted June 5, 2014 Author Share Posted June 5, 2014 Hehehe - I did nothing other than loading the cart through the MESS UI file manager. As soon as I hit enter the whole system locks up. I'm running v1.53 at the moment. The cart is the one from the whtech: ftp://ftp.whtech.com/emulators/cartridges/rpk/as_robotron_2084.rpk Quote Link to comment Share on other sites More sharing options...
RobertLM78 Posted June 5, 2014 Author Share Posted June 5, 2014 This version works fine for me. It is a zipped MESS (rpk) file. Interesting. Check these md5sums out: 3b56b6da61135a1a38cdc6974fab35ef as_robotron_2084.rpk (from whtech) c6b78488bc1ad61c6eb43c892c33759c as_robotron_2084.zip (your attachment) I'll give this one a go. If I suddenly disappear for a moment, you'll know why . Quote Link to comment Share on other sites More sharing options...
RobertLM78 Posted June 5, 2014 Author Share Posted June 5, 2014 (edited) Well, that's good, no crash, but says 'internal error': Edit: Nevermind - I didn't realize that you'd zipped the rpk, I figured you had just changed the extension . This would also explain the differing md5sums. Hmm, where did you get this version, Rasmus, whtech? The md5sums are identical now, so I wonder if I'm about to crash my system for no reason . Edited June 5, 2014 by RobertLM78 Quote Link to comment Share on other sites More sharing options...
+mizapf Posted June 5, 2014 Share Posted June 5, 2014 The attached zip file is really a zip file, containing the rpk. Did you just rename zip to rpk? Quote Link to comment Share on other sites More sharing options...
RobertLM78 Posted June 5, 2014 Author Share Posted June 5, 2014 Well, I've even extracted the .bin files from 'both' versions to see if there was a difference in those, and there are none. I think I'll wait for a report back from Rasmus before I try it - I'm not keen on having to forceably restart my computer. The attached zip file is really a zip file, containing the rpk. Did you just rename zip to rpk? That's exactly what I had done . Quote Link to comment Share on other sites More sharing options...
+mizapf Posted June 5, 2014 Share Posted June 5, 2014 I actually found an issue in the MAME core which causes a crash on exit; already posted it on the mamedev list. But I can always reset the emulator using F3 in partial mode. Are you running it on Linux? Quote Link to comment Share on other sites More sharing options...
RobertLM78 Posted June 5, 2014 Author Share Posted June 5, 2014 I actually found an issue in the MAME core which causes a crash on exit; already posted it on the mamedev list. But I can always reset the emulator using F3 in partial mode. Are you running it on Linux? I'm running MESS on Linux Mint 13 (64-bit). Everything freezes when it crashes - I can't even go tty. I doubt the F3 reset would do me much good at that point . Quote Link to comment Share on other sites More sharing options...
RobertLM78 Posted June 5, 2014 Author Share Posted June 5, 2014 Something that strikes me as odd is that all the other Atarisoft titles appear to work normally. Quote Link to comment Share on other sites More sharing options...
Tursi Posted June 5, 2014 Share Posted June 5, 2014 Honestly, I'm not sure how .BIN files are made. I've seen the "Cart conversion by Tursi" before, but figured it was for the specific cart (DM 2000). If it is just a bad conversion, we should fix that, because it's affecting at least 2 emulators, and probably more I'd figure. That's only for EA#5 files converted to load from GROM with my tool, Robotron started life as a cartridge so won't have that. 1 Quote Link to comment Share on other sites More sharing options...
+mizapf Posted June 5, 2014 Share Posted June 5, 2014 I'm running MESS on Linux Mint 13 (64-bit). Everything freezes when it crashes - I can't even go tty. I doubt the F3 reset would do me much good at that point . In that case it's likely your system at fault, possibly the graphics card driver. An application like MESS should not be able to cause a freeze, yet it's still possible that it triggers the bug. Can you still do a dmesg or check your /var/log/Xorg.0.log for evidence that there is a crash somewhere? Maybe keep a terminal window open on the desktop. Quote Link to comment Share on other sites More sharing options...
+mizapf Posted June 5, 2014 Share Posted June 5, 2014 (edited) Ah, I just noticed that the Robotron ROMs are overdumped, i.e. there are trailing zeros (check their lengths). So that is the point where they differ from other Atarisoft cartridges. Here is a new RPK; try that one as_robotron_2084.rpk Edited June 5, 2014 by mizapf 1 Quote Link to comment Share on other sites More sharing options...
RobertLM78 Posted June 5, 2014 Author Share Posted June 5, 2014 (edited) Here's my Xorg.0.log and the output from dmesg. I'm not sure what to look for in those, I must admit. I will go ahead and open mess in a terminal, and report back. I'll also add the new Xorg.0.log and dmesg output (assuming it will crash). Are you sure that it's my hardware? I've never had this happen with any other cart, and I can't imagine what would make this one so special. Edit: Ah, I just noticed that the Robotron ROMs are overdumped, i.e. there are trailing zeros (check their lengths). So that is the point where they differ from other Atarisoft cartridges. Here is a new RPK; try that one I'll try this one first . Xorg.0.log.txt dmesg.txt Edited June 5, 2014 by RobertLM78 Quote Link to comment Share on other sites More sharing options...
RobertLM78 Posted June 5, 2014 Author Share Posted June 5, 2014 (edited) Well Michael, the good news is that the new cart does not freeze up the host system. The bad news is that the game blue screens after the 'tunnel' sequence and I have to do an F3 reset . Edit. Edited June 5, 2014 by RobertLM78 Quote Link to comment Share on other sites More sharing options...
+mizapf Posted June 6, 2014 Share Posted June 6, 2014 (edited) Yes, as I wrote in another thread, Robotron is not stable. Classic99 seems to have similar problems with it. The dumps you uploaded do not show any evidence of a crash; did you copy them immediately when your system froze? (... wait, this sounds somewhat silly ... ) If you look at the Xorg.0.log after a reboot, it doesn't have the stack trace of the previous run; in that case we need the Xorg.0.log.old. You're using the fglrx driver, which I'm also using, but it seems as if mine is more recent: "module version = 14.10.2". Edited June 6, 2014 by mizapf Quote Link to comment Share on other sites More sharing options...
RobertLM78 Posted June 6, 2014 Author Share Posted June 6, 2014 (edited) Yes, as I wrote in another thread, Robotron is not stable. Classic99 seems to have similar problems with it. The dumps you uploaded do not show any evidence of a crash; did you copy them immediately when your system froze? (... wait, this sounds somewhat silly ... ) If you look at the Xorg.0.log after a reboot, it doesn't have the stack trace of the previous run; in that case we need the Xorg.0.log.old. You're using the fglrx driver, which I'm also using, but it seems as if mine is more recent: "module version = 14.10.2". I think I downloaded 14.x - maybe I'll give it a shot. I know that one of the driver 'upgrades' I installed wasn't much of an improvement - I figured if it's not broke, don't fix it, so I have just frozen the driver at version 13.x. My guess is now that I've restarted the computer a couple of times, the logs have been overwritten. What I could do is next time I go to restart the system, I'll fire up MESS in a terminal and try to insert the whtech version of RoboTron, if you're still interested in knowing about why I'm getting the freeze. By unstable, do you mean just bad .bin images, or something even deeper than that (i.e., something do with the physical cart itself)? Edited June 6, 2014 by RobertLM78 1 Quote Link to comment Share on other sites More sharing options...
am1933 Posted June 6, 2014 Share Posted June 6, 2014 I think I downloaded 14.x - maybe I'll give it a shot. I know that one of the driver 'upgrades' I installed wasn't much of an improvement - I figured if it's not broke, don't fix it, so I have just frozen the driver at version 13.x. My guess is now that I've restarted the computer a couple of times, the logs have been overwritten. What I could do is next time I go to restart the system, I'll fire up MESS in a terminal and try to insert the whtech version of RoboTron, if you're still interested in knowing about why I'm getting the freeze. By unstable, do you mean just bad .bin images, or something even deeper than that (i.e., something do with the physical cart itself)? As much as I admire your tenacity and as much as I love Robotron, I think you would be quicker building a M.A.M.E cabinet from scratch. 1 Quote Link to comment Share on other sites More sharing options...
+mizapf Posted June 6, 2014 Share Posted June 6, 2014 By unstable, do you mean just bad .bin images, or something even deeper than that (i.e., something do with the physical cart itself)? Even worse: Game code is buggy. 1 Quote Link to comment Share on other sites More sharing options...
+Ksarul Posted June 6, 2014 Share Posted June 6, 2014 Is this a dump from one of the Competition Computers ROMs for Robotron or was it from a different prototype? There were several different prototypes out there, so maybe one of them is less buggy. I remember talking to Kyle about this one back in 1996 and he said the ROM he got initially was suffering from bit rot--and that he had to compare several to get an undamaged copy out of the mess. He got a lot of stuff from Atari back then--and I suspect his reconstruction was based on some partial source code access. . . 1 Quote Link to comment Share on other sites More sharing options...
marc.hull Posted June 6, 2014 Share Posted June 6, 2014 Even worse: Game code is buggy. Robotron as played on my TI99 does not show any obvious bugs at all. The symptoms complained about do not exist on the real deal as far as my experience shows. Just played it for about an hour, again, and had no issues other than it get pretty difficult pretty quick and using one controller is a handicap. I dumped the ROM a while back and posted it but it was the same one that Mike thought was buggy. In fact I am pretty sure that there is only one available as it was dumped just a couple of years back. Evidently Robotron does something that is fooling you Emu curators. The game works flawlessly on a real TI99/4a and as far as I understand that's the metal test...... 1 Quote Link to comment Share on other sites More sharing options...
RobertLM78 Posted June 6, 2014 Author Share Posted June 6, 2014 The game works flawlessly on a real TI99/4a and as far as I understand that's the metal test...... I agree. So the .rpk on whtech was made from those dumps a couple of years ago? (Incidentally, the date of the upload to whtech was January 2013, so it could well be). Ah well, it was worth looking into. It would still be good to find out why MESS dislikes it so much (at least for us 'Emu Curators' ). Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.