+DZ-Jay Posted January 7, 2017 Share Posted January 7, 2017 (edited) Happy New Year! 2017 has started and with it comes a new version of the IntyBASIC SDK for Windows. The new year is off to a good start so far. SDK v1.1.1 (eleventy-one) I know I've made you all wait long enough, and in fact this version of the SDK has been (mostly) ready since Summer 2015 waiting for me to complete the Mac version. So, in the interest of advancing the state-of-the-art as we go along, I've decided to release what I have ready. Sorry Mac users, you will have to wait a bit longer. This edition adds many fixes to the tools discovered on the first release and adds a host of new features. One notable new addition is a default Mattel-style title screen with the name of the program and copyright notice with the author's name. New projects created will include this title screen automatically unless explicitly suppressed. It also includes the latest version of IntyBASIC and its libraries and the latest build tools from the SDK-1600. Needless to say, we've heard all the comments and feedback, and we've tried hard to make this version of the SDK even easier to use and more powerful. If you are a brand new user, you just download and install the SDK and off you go. If you have an earlier version of the SDK, you can just uninstall it and install the new one. The installer will automatically detect a previous version and attempt to uninstall it first. The SDK has always been designed with future updates in mind, so it should be completely safe to replace older versions with newer ones. When uninstalling, all folders will be removed except the "Projects" folder, which should carry on to the next version. If you made any modifications to any files of the distribution, they will also not be removed. However, they will be replaced automatically with newer versions when you upgrade. You can get the latest version of the SDK in the official IntyBASIC SDK thread. Like always, if you have any questions or problems, just post them here. Happy coding! -dZ. Changes in this version v1.1.1 Jan/08/2017 Added infinite loop to INTYNEW template to avoid “falling through” at the end. Users can now select destination folder during installation. INTYDBUG did not enable the debugger correctly. Updated all tools to support usage help invocation. Updated INTYNEW to accept “Author” argument and generate default Mattel-style title screen. Fixed argument extraction bugs in tools. Added new program “classic” to demonstrate the default classic title screen, in “Examples” folder. Added new option to INTYNEW to suppress default title screen. Updated to the latest version of IntyBASIC distribution (v1.2.. Updated to the latest version of the SDK-1600 binary tools. Included the latest “constants.bas” library file (v1.24F). Added support for Windows Server 2008 and 2012. ... and more! Edited January 8, 2017 by DZ-Jay 6 Quote Link to comment Share on other sites More sharing options...
fsuinnc Posted January 7, 2017 Share Posted January 7, 2017 Awesome! Thanks. Happy New Year! 1 Quote Link to comment Share on other sites More sharing options...
+DZ-Jay Posted January 7, 2017 Author Share Posted January 7, 2017 I've fixed a stupid issue with the IntyNEW tool, so if you downloaded version eleventy-one, I urge you to re-download and re-install it. Quote Link to comment Share on other sites More sharing options...
fsuinnc Posted January 7, 2017 Share Posted January 7, 2017 I created a new project and then did build and run and oddly the yellow and red color bars are missing. When I removed the comments about left and right vertical bars that are on the print lines for the bars in the Title.bas, the bars show as expected. Odd. Not sure what might cause this. Quote Link to comment Share on other sites More sharing options...
+DZ-Jay Posted January 7, 2017 Author Share Posted January 7, 2017 I created a new project and then did build and run and oddly the yellow and red color bars are missing. When I removed the comments about left and right vertical bars that are on the print lines for the bars in the Title.bas, the bars show as expected. Odd. Not sure what might cause this. shot0000.gif I got the same thing, but it's only in the latest version of IntyBASIC. The older one actually built it correctly. When I look at the ASM file created, the lines in between are not assembled. In fact, they are nowhere to be found! IntyBASIC Source: ' Print classic colored bars PRINT AT SCREENPOS( 2, COLOR_BAR_ROW) COLOR CS_WHITE, "\165" ' \ PRINT AT SCREENPOS( 4, COLOR_BAR_ROW) COLOR CS_YELLOW, "\165" ' |_ Vertical bar on left PRINT AT SCREENPOS( 6, COLOR_BAR_ROW) COLOR CS_GREEN, "\165" ' | PRINT AT SCREENPOS( 8, COLOR_BAR_ROW) COLOR CS_DARKGREEN, "\165" ' / PRINT AT SCREENPOS(11, COLOR_BAR_ROW) COLOR CS_TAN, "\164" ' \ PRINT AT SCREENPOS(13, COLOR_BAR_ROW) COLOR CS_RED, "\164" ' |_ Vertical bar on right PRINT AT SCREENPOS(15, COLOR_BAR_ROW) COLOR CS_BLUE, "\164" ' | PRINT AT SCREENPOS(17, COLOR_BAR_ROW) COLOR CS_BLACK, "\164" ' / Assembly source: ;[86] ' Print classic colored bars SRCFILE "title.bas",86 ;[88] PRINT AT SCREENPOS( 2, COLOR_BAR_ROW) COLOR CS_WHITE, "\165" ' PRINT AT SCREENPOS( 4, COLOR_BAR_ROW) COLOR CS_YELLOW, "\165" ' |_ Vertical bar on left SRCFILE "title.bas",88 MVII #534,R0 MVO R0,_screen MVII #7,R0 MVO R0,_color MVI _screen,R4 MVII #1320,R0 XOR _color,R0 MVO@ R0,R4 MVO R4,_screen ;[89] PRINT AT SCREENPOS( 6, COLOR_BAR_ROW) COLOR CS_GREEN, "\165" ' | SRCFILE "title.bas",89 MVII #538,R0 MVO R0,_screen MVII #5,R0 MVO R0,_color MVI _screen,R4 MVII #1320,R0 XOR _color,R0 MVO@ R0,R4 MVO R4,_screen ;[90] PRINT AT SCREENPOS( 8, COLOR_BAR_ROW) COLOR CS_DARKGREEN, "\165" ' / SRCFILE "title.bas",90 MVII #540,R0 MVO R0,_screen MVII #4,R0 MVO R0,_color MVI _screen,R4 MVII #1320,R0 XOR _color,R0 MVO@ R0,R4 MVO R4,_screen ;[91] SRCFILE "title.bas",91 ;[93] PRINT AT SCREENPOS(11, COLOR_BAR_ROW) COLOR CS_TAN, "\164" ' PRINT AT SCREENPOS(13, COLOR_BAR_ROW) COLOR CS_RED, "\164" ' |_ Vertical bar on right SRCFILE "title.bas",93 MVII #543,R0 MVO R0,_screen MVII #3,R0 MVO R0,_color MVI _screen,R4 MVII #1312,R0 XOR _color,R0 MVO@ R0,R4 MVO R4,_screen ;[94] PRINT AT SCREENPOS(15, COLOR_BAR_ROW) COLOR CS_BLUE, "\164" ' | SRCFILE "title.bas",94 MVII #547,R0 MVO R0,_screen MVII #1,R0 MVO R0,_color MVI _screen,R4 MVII #1312,R0 XOR _color,R0 MVO@ R0,R4 MVO R4,_screen ;[95] PRINT AT SCREENPOS(17, COLOR_BAR_ROW) COLOR CS_BLACK, "\164" ' / SRCFILE "title.bas",95 MVII #549,R0 MVO R0,_screen CLRR R0 MVO R0,_color MVI _screen,R4 MVII #1312,R0 XOR _color,R0 MVO@ R0,R4 MVO R4,_screen ;[96] 1 Quote Link to comment Share on other sites More sharing options...
+DZ-Jay Posted January 7, 2017 Author Share Posted January 7, 2017 Got it! It's strange behaviour of the new "\" line concatenation operator. I think it should not be applied within a line comment. -dZ. Quote Link to comment Share on other sites More sharing options...
mmarrero Posted January 7, 2017 Share Posted January 7, 2017 I'm trying the SDK for the 1st time, and refuses to install on Win Server 2012R2, even with compatibility settings. (Don't worry, I'll run in on a VM). It's a common issue in Win Server, for example Microsoft's own Zune software also didn't install... Ironically, Win Server is still free for College students via Dreamspark, and, years ago a Microsoft recruiter e-mailed me about that job position. They chose poorly. Lol. Quote Link to comment Share on other sites More sharing options...
+DZ-Jay Posted January 7, 2017 Author Share Posted January 7, 2017 I'm trying the SDK for the 1st time, and refuses to install on Win Server 2012R2, even with compatibility settings. (Don't worry, I'll run in on a VM). It's a common issue in Win Server, for example Microsoft's own Zune software also didn't install... Ironically, Win Server is still free for College students via Dreamspark, and, years ago a Microsoft recruiter e-mailed me about that job position. They chose poorly. Lol. I haven't tested the compiler nor the tools in Win Server 2012. If they work, I can modify the installer to allow installation. Can someone confirm that IntyBASIC and jzIntv run in Win Server 2012? -dZ. Quote Link to comment Share on other sites More sharing options...
fsuinnc Posted January 7, 2017 Share Posted January 7, 2017 Thanks. I should have paid more attention to the assembly source and noticed that. Must suck when you try and give us all an updated tool and all I do is complain. Sorry about that. (but I am pretty lost without your SDK) Quote Link to comment Share on other sites More sharing options...
+DZ-Jay Posted January 7, 2017 Author Share Posted January 7, 2017 Thanks. I should have paid more attention to the assembly source and noticed that. Must suck when you try and give us all an updated tool and all I do is complain. Sorry about that. (but I am pretty lost without your SDK) No, no, no, I really want to hear the feedback, so complaint all you want. The SDK is for the community and it is only worth it as long as it is valuable. I personally don't use IntyBASIC, but I really want it to be accessible to everyone. So, keep all the feedback coming and make sure you point out any problems or issues you encounter. And if you have any recommendations, bring them on! -dZ. Quote Link to comment Share on other sites More sharing options...
mmarrero Posted January 8, 2017 Share Posted January 8, 2017 I haven't tested the compiler nor the tools in Win Server 2012. If they work, I can modify the installer to allow installation. Can someone confirm that IntyBASIC and jzIntv run in Win Server 2012? Yes, both jzintv and IntyBasic work perfectly in Server 2012. (I just recompiled and ran IntyMusic to make sure). Think of "Windows Server" as a variant of the old "Windows NT Workstation", which is now Windows Home, Pro, and Enterprise. I don't think of a technical reason for Win8 software not being able to run in Server 2012. (The only major issue I've seen is legacy software, Server has Data Execution Prevention (DEP) fully enabled by default). 1 Quote Link to comment Share on other sites More sharing options...
+DZ-Jay Posted January 8, 2017 Author Share Posted January 8, 2017 Yes, both jzintv and IntyBasic work perfectly in Server 2012. (I just recompiled and ran IntyMusic to make sure). Think of "Windows Server" as a variant of the old "Windows NT Workstation", which is now Windows Home, Pro, and Enterprise. I don't think of a technical reason for Win8 software not being able to run in Server 2012. (The only major issue I've seen is legacy software, Server has Data Execution Prevention (DEP) fully enabled by default). OK, I'll include support for Windows Server 2012. I will also patch the title screen to work around the issue of escaping EOL within a comment, which I'm trying to convince Oscar to fix in IntyBASIC (since it is not "C," it breaks existing code, and it's just plain weird). Oscar is very busy with other things at the moment, so it will be several months before IntyBASIC is updated. In the meantime, all you have to do is avoid ending a comment line with "\", and if you do, just add a space afterwards. Is there any other request for features or bug fixes I should include? -dZ. Quote Link to comment Share on other sites More sharing options...
+DZ-Jay Posted January 8, 2017 Author Share Posted January 8, 2017 Alright, campers! I've updated the release and bumped it up to 1.1.1 (which is now truly "eleventy-one"). This version works around the issue of escaping end-of-lines in comments introduced by the IntyBASIC feature of "line concatenation." This only affected the new default Mattel-style title screens, making every other coloured bar disappear. The work-around consists in just avoiding ending comment lines with "\". The other change was adding support for Windows Server 2008 and 2012, with the expectation that the compiler tools actually work (confirmed by mmarrero, thanks!). I recommend everybody using IntyBASIC SDK to upgrade to this new version. If you downloaded the previous one yesterday (v1.1.0), and you don't want to upgrade, let me know and I'll show you easily how to "patch" your existing version to solve the title screen issue in new and existing projects. Although, really, it's easier to just re-run the new installer. I've updated the first post in the official thread with the latest distribution of the SDK. I think this is it... for now. -dZ. 1 Quote Link to comment Share on other sites More sharing options...
+DZ-Jay Posted January 8, 2017 Author Share Posted January 8, 2017 (edited) As an illustration, below is the default "Mattel-style" title screen included in new projects. This is from the example "Classic" in the "Examples" project, which was created with the following command-line: > INTYNEW "Classic Title" "Nobody" The first argument to INTYNEW is the name of the project. This will be the name of the folder within the "Projects" folder, the name of the source file, and the name in the title screen. The second argument is the author, which will be included in the header comments of the source file and in the copyright notice of the title screen. This is automatically created for every new project unless you include the command-line option "/s" to suppress the title screen generation. To modify the title screen, just open up the "title.bas" source file created by INTYNEW as part of your project. This file has lots of comments specifying what everything does, so it should be easy to modify. -dZ. Edited January 8, 2017 by DZ-Jay 1 Quote Link to comment Share on other sites More sharing options...
MoonTurtle Posted September 22, 2018 Share Posted September 22, 2018 Is there a tutorial for IntyBASIC? Also, is this program entirely run through command line, right now I'm on the Command Console, (C:\IntyBASIC SDK>) and I don't know exactly what to do. Quote Link to comment Share on other sites More sharing options...
mmarrero Posted September 23, 2018 Share Posted September 23, 2018 Is there a tutorial for IntyBASIC? Also, is this program entirely run through command line, right now I'm on the Command Console, (C:\IntyBASIC SDK>) and I don't know exactly what to do. There's a tutorial, in the Start Menu look or trpe "IntyBASIC SDK Tools Usage Guide.rtf" which is in the IntyBasic SDK folder/section. To summarize, from the command-line, just do each of the 4-5 steps: REM To create a new IntyBasic from scratch REM Please note that IntyNew auto-sets your current directory to "MyProject" INTYNEW MyProject "My Inty Project" REM When you launch from the SDK command-line, Change Directory to the project folder! CD "MyProject" REM Let's edit the source file, using the 2nd worst text editor ever made Notepad MyProject.Bas REM Let's compile the program. If there are 0 Errors, it's read to run INTYBUILD MyProject REM Let's run the program INTYRUN MyProject I absolutely recommend a good text editor, I recommend "Visual Studio Code". There was a topic discussion in here about other great editors.There's also an IDE for IntyBasic somewhere, but I haven't used it. Quote Link to comment Share on other sites More sharing options...
MoonTurtle Posted September 23, 2018 Share Posted September 23, 2018 Thank You! I was kinda lost on that command prompt, Why is Notepad terrible? I've used it for for a while now, and it seems just fine to me, (it does seem a bit bare-bones, as in there isn't much there for you to do,) I mainly just use it for creating and editing .txt and .ini files. Also, do Intellivision Lives! and Intellivision Revolution do what AtariAge do, and actually produce new cartridges for new homebrew games for the system? just wondering, Quote Link to comment Share on other sites More sharing options...
intvnut Posted September 24, 2018 Share Posted September 24, 2018 Why is Notepad terrible? I've used it for for a while now, and it seems just fine to me, (it does seem a bit bare-bones, as in there isn't much there for you to do,) I mainly just use it for creating and editing .txt and .ini files. Notepad is a serviceable basic text editor. It's just rather weak. If you've ever used a text editor with decent functionality, going back to Notepad feels like going back to pen and paper, with a pen that keeps drying out randomly and needs tapping on a hard surface. If nothing else, Notepad doesn't handle UNIX formatted files. (Or, at least didn't. Maybe they've fixed that finally, after decades.) Go look up Notepad++. It made my life much happier in Windows land, when I needed to be there. I'm also partial to VIM; however, if you're already not comfortable with the command line, I can't in good conscience recommend trying VIM unless you're eager to jump down the rabbit hole. Also, do Intellivision Lives! and Intellivision Revolution do what AtariAge do, and actually produce new cartridges for new homebrew games for the system? just wondering, There are multiple folks that produce cartridge versions of homebrew titles, as well as modern-age licensed releases. Elektronite produces licensed games. Rev produces homebrew titles. There isn't really a vanity press service at the moment, where someone can show up with a ROM and ask for X copies of it in cartridge format. I do have a cartridge design (JLP) that would support that though, and have some ideas in that direction. I've produced the occasional one-off for individuals, and I provide production cartridge runs for Elektronite and others from time-to-time. My board design is not the only game in town, of course. 5-11under has a design, and intvdave (IntelligentVision) has a design. The site "intellivisionlives.com" is the Intellivision Productions website. Intellivision Productions has not released any cartridge versions of their Intellivision catalog thus far, although they have released titles for other platforms (Steamroller on ColecoVision). With the advent of Intellivision Entertainment, it's fair to say the current situation is in flux. I'd say "Watch this space," if for no other reason than that there seems to be a much more open stance toward the community. Bill Fisher has announced a programming contest for Intellivision where they're opening up the EXEC. That's a first! I expect interesting developments to come out of the Intellivision Productions => Intellivision Entertainment evolution. 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.