This small update fixes a problem with IX/IY register handling. Once again, thanks to Optimus for providing the patch ! SDCC2Pasmo v1.7 (binary + sources) is available in Productions section of this website.
This is a new version of Phactory, a powerful development environment targeting Amstrad CPC (Windows-only).
The most noticeable changes: revamped user interface, overall speed improvements thanks to new plugin system, a new source code editor featuring Z80 assembly syntax highlighting, and finally some minor bug fixings.
Unfortunately, this program is still not ready for prime time, since there is still no documentation, no examples / project templates, and no support for it for the moment. One day, maybe..
Still, if you are curious enough, go get it here (Phactory is also listed in Productions section).
This might not be the best code I ever done, but at least, it does the job pretty well : SDCC2Pasmo takes as input a .asm file generated while compiling C code with SDCC, and outputs an other .asm file that is compatible with Pasmo, Maxam or WinAPE assembler syntax.
Command-line usage: SDCC2Pasmo sdcc_output.asm pasmo_compatible.asm.
C++ sources for Windows are now available through Productions section of this website, so feel free to recompile it for your favorite development environment if you need to.
I finally decided to release my own IDE, called Phactory. It's basically a program that allows to create Amstrad CPC productions without using third-party tools : everything is integrated into the same user interface. The whole development chain is supported : developer can create a new C source file, that will get compiled to ASM, this ASM file can then be compiled to a BINARY file, that binary file can then be compressed then injected into a DSK file that can also be converted later to HFE... and I did not even talk about data converters (bitmap handling, packers, text to charset indices, etc).
Bad news for you is the following disclaimer : this IDE has been created by me, for me. I have (profesional) experience in releasing programs used by others; I'm completely aware of the high level of support required for such a program. Due to that, and I'm pretty serious about this, I WON'T BRING ANY KIND OF SUPPORT TO THIS PROGRAM. Please don't even ask for new features, explanations or whatever. Hope you understand my position.
So.. for the others that may be interested in testing Phactory ;-) Since there is no dedicated documentation (yet), I will give you here the first steps. Basically, Phactory behaves like Visual Studio does. First, make sure you installed SDCC on your system, as also .Net framework 3.5 (or newer version). Then launch Phactory. Create a new project via File / New Project. In the Project Explorer, you folders have been created for you. By right-clicking on folders, you can have actions to create new resources. Choose "Assembly source file". Then still in Project Explorer, double-click on the freshly created file and create a small ASM program. Make sure to start it with org &4000 (of course you can set any org value here, later). Ctrl+S to save the program. Now right-click on a folder in Project Explorer, create a new Disk file resource (cpcdsk). Double-click on new created resource, click Add.. and then select the output of your ASM file (expected extension is .bin). Save it (Ctrl+S). Now go in Tools/Options and make sure to uncheck "Hide unused resources". Unused resources (output files are also resources !) now appears in Project Explorer. Locate the resource having ".dsk" extension. Right-click on it and select "Set as startup resource". From now, every times you will press the F5 key, it will resolve all dependencies starting for the startup resource, build the resource that changed and will finally run the startup resource ! The "run" feature on "dsk" is binded to WinAPE emulator.
Basically, that's it. Hate it or love it ! ;-) Phreaks, QuickCMD... could not exist without this program. I really fell myself so productive using it. Be curious ! And keep in mind : no support from me at all....
Download link can be found on official Phactory page, also available in Productions section.
And here we go again for a new tool release ! This time it's QuickCMD that got updated to version 2.3.
This adds support for a new command history to be used through UP and DOWN keys (was requested by many of you !). Also, a critical crash has been fixed with ROMS command when listing ROMs having corrupted names. Another critical problem (involving stability) has been fixed with direct drive parsing. And finally, the RSX got renamed to |Q for even faster switching from BASIC to QuickCMD.
As usual, if you experience problems or whatever, feel free to contact me. Last version can be downloaded here (also available in Productions section).
Thanks to Gryzor, CanonMan and Terje_Norway from CPCWiki that reported the issue, there is now a new released version of the HxC Floppy Emulator Manager. Only one change : it adds auto-detection of the HxC Floppy Emulator device when configured as drive B. You can download it here (also available in the Productions section).
Version 2.3 of HxC Floppy Emulator Manager just got released here. It's now faster to launch, spaces in directory names can now be used, and the user interface is now using the default system font with new color scheme (aligned to ParaDOS and QuickCMD's ones). As previous releases, ROM version is also available. If you experience issues with the software, please report them on the cpcwiki's dedicated thread. Your feedback is important to us ! :)
A new version of QuickCMD, a shell-like user interface for disc-based Amstrad CPC computers, is available here.
These are the changes:
- Added support for Bryce's MegaFlash
- Renamed RO and RW commands to READONLY and READWRITE
- Removed CRTC command
- Reset screen to QuickCMD’s default if external RSX changed video mode
- DELROM now clears a rom with &FF value (was using &00)
- Fixed: was overwriting first byte after HIMEM
- Fixed: not assuming anymore than Amsdos area is always at &A700
If you want more information about QuickCMD (a documentation is also available as a .PDF file), feel free to read its dedicated webpage.