JagChris Posted July 23, 2012 Share Posted July 23, 2012 Has any more progress been made on this? Quote Link to comment Share on other sites More sharing options...
GroovyBee Posted July 23, 2012 Author Share Posted July 23, 2012 Has any more progress been made on this? I haven't had time to look at the rest of the issues with the removers library but anybody can pick up the baton if they like. Quote Link to comment Share on other sites More sharing options...
JagChris Posted October 16, 2012 Share Posted October 16, 2012 I'd agree with GB above, use VirtualJaguar instead of Jagulator. Jagulator is more flexible in what you can point it at to load up. Quote Link to comment Share on other sites More sharing options...
GroovyBee Posted October 16, 2012 Author Share Posted October 16, 2012 Jagulator is more flexible in what you can point it at to load up. Personally I'd pick the more accurate emulation in Virtual Jaguar over ease of loading in Jagulator any day of the week. You can easily pad ROMs to the size you need using Reboot's JIFFI or create your own custom tools to do the job (like I did) or if really pushed you could even use a hex editor and do it manually. 1 Quote Link to comment Share on other sites More sharing options...
JagChris Posted October 16, 2012 Share Posted October 16, 2012 Personally I'd pick the more accurate emulation in Virtual Jaguar over ease of loading in Jagulator any day of the week. You can easily pad ROMs to the size you need using Reboot's JIFFI or create your own custom tools to do the job (like I did) or if really pushed you could even use a hex editor and do it manually. Thats not very practical if you just want to see the results of a simple change you made. But to each their own. Quote Link to comment Share on other sites More sharing options...
+CyranoJ Posted October 16, 2012 Share Posted October 16, 2012 Thats not very practical if you just want to see the results of a simple change you made. But to each their own. And that's why we have batch files. One command, assemble, link, pad, copy to VJ/SOFTWARE, call VJ in alpine mode. It's not rocket science 3 Quote Link to comment Share on other sites More sharing options...
Tyrant Posted October 16, 2012 Share Posted October 16, 2012 JIFFI can be driven from the command line, so you can add it into your build script / makefile. Easy. 1 Quote Link to comment Share on other sites More sharing options...
JagChris Posted October 16, 2012 Share Posted October 16, 2012 In time I'll probably be forced to do all that. Quote Link to comment Share on other sites More sharing options...
+Gemintronic Posted October 29, 2012 Share Posted October 29, 2012 In time I'll probably be forced to do all that. If batch files feel wrong then you can be the first to correct it. Install AutoIt and create a nice executable to wrap this stuff around. That way you could be the first and last newbie to deal with this. Quote Link to comment Share on other sites More sharing options...
JagChris Posted October 30, 2012 Share Posted October 30, 2012 Yeah thats cool. I guess it would be totally nuts to request that VJ in the future be less picky about what you can point it at? Quote Link to comment Share on other sites More sharing options...
+Gemintronic Posted October 30, 2012 Share Posted October 30, 2012 Yeah thats cool. I guess it would be totally nuts to request that VJ in the future be less picky about what you can point it at? You're right. So are they. Different world view. Different ideas on what constitutes flexible and easy. You've got a chance to build on their work and bring it up to your standards. 3 Quote Link to comment Share on other sites More sharing options...
+CyranoJ Posted October 30, 2012 Share Posted October 30, 2012 Yeah thats cool. I guess it would be totally nuts to request that VJ in the future be less picky about what you can point it at? If you read the manual and start it with --alpine it'll load anything you point at it. Even Atari ST games! 4 Quote Link to comment Share on other sites More sharing options...
ST-Oldie Posted October 27, 2013 Share Posted October 27, 2013 Hi, Most of the hurdles to programming the jag in "C" using windows xp with a standard library available and the Removers library have been solved :-http://www.jagware.org/index.php?s=&showtopic=1003&view=findpost&p=14826 I have written an "addon" with informations about my modification on jlibc for use on my linux development with vbcc: using jlibc-0.5.10 with vbcc for Jaguar Development 2 Quote Link to comment Share on other sites More sharing options...
GroovyBee Posted October 27, 2013 Author Share Posted October 27, 2013 I have written an "addon" with informations about my modification on jlibc for use on my linux development with vbcc: using jlibc-0.5.10 with vbcc for Jaguar Development Brilliant! I'll check out your changes when I have some free time. Quote Link to comment Share on other sites More sharing options...
JagChris Posted October 28, 2013 Share Posted October 28, 2013 So this is not really a continuation of your work on getting Sebs library working under Windows is it? Quote Link to comment Share on other sites More sharing options...
ST-Oldie Posted October 28, 2013 Share Posted October 28, 2013 Hi, So this is not really a continuation of your work on getting Sebs library working under Windows is it? Because i am not GroovyBee no, but also a little bit yes. The jlibc did not work on Windows, it work on the Jaguar! But it depends also on the compiler you use. I have made some changes in the jlibc for use this library with vbcc. You can see these changes as a continuation and we can merge my changes with some missing changes of GroovyBee. I did not take care where the DATA section is located to have a lib for RAM or cartridge use. But this is a minor change in the start.c file. These changes did not depend on the OS of your development system. They only depend on the compiler you use. Maybe we can add some of the changes in the original package of Seb to allow the use for gcc and vbcc. But changes for the build process are not in my patch. I work with linux so i was able to use the original makefiles. I have only changes in the makefile for additional files and different settings for vbcc. Best regards Michael 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.