forum.defence-force.org

Questions, bug reports, features requests, ... about the Oric Software Development Kit. Please indicate clearly in the title the related element (OSDK for generic questions, PictConv, FilePack, XA, Euphoric, etc...) to make it easy to locate messages.

This update should please Xeron, but also people having performances issues on Windows 7 and Vista.

Version 0.20 - April the 8th 2012
- Oricutron 0.9 is now used by default instead of Euphoric, you can set OSDKEMUL to choose between EUPHORIC and ORICUTRON.

This is correct. I did not change anything else, this version is totally identically to the OSDK 0.19, all I did was to add Oricutron (Euphoric is still present) which allows us to handle three situations:
- Euphoric
- Euphoric through DosBox
- Oricutron

The first scenario works for people using Windows 98, kind of work on Windows XP, and totally does not work on Windows 2000, Windows Vista or Windows 7.
The second scenario works for about everybody, except that using Euphoric through DosBox makes the performance drop quite a lot, which can be a problem for people using old machines.
The third situation is optimal, because it brings us a native Windows 32 application, which runs nicely on all version of Windows, from Windows 95 to Windows 7, and from 32 bit to 64 bit setups.

In order to exploit this new system, you need to do a minor change to your osdk_execute.bat files, instead of calling %OSDK%\Euphoric\osdk_euphoric.bat you need to call %OSDK%\bin\execute.bat.

The original batch file is still there, so it will not stop your code to work, just that it will still call Euphoric.

If this version 0.20 works nicely, I will try to update the other components (like Old2MFM, Tap2CD, etc...) which are not Windows 7 friendly, so hopefully at some point the whole tool-chain will be usable on recent 64 bit windows.

I strongly advice you to install it on the side of the version your already use, just change your OSDK variable to point to the new folder, and if anything happens to not work, please signal the issue here, and continue to use your previous version instead.

Just made a first quick test of OSDK 0.20. It compiles Skool Daze smoothly and correctly. Disk-based tools still give me problems under win64 (tap2dsk and old2mfm are called). Changed the make.bat to call dsktool and it worked.

Also when selecting Oricutron to execute the compiled file, it fails as it does not have the roms folder and the image folder is empty. Copied all the folders I have in Oricutron there, and I made it work...

Just made a first quick test of OSDK 0.20. It compiles Skool Daze smoothly and correctly. Disk-based tools still give me problems under win64 (tap2dsk and old2mfm are called). Changed the make.bat to call dsktool and it worked.

Also when selecting Oricutron to execute the compiled file, it fails as it does not have the roms folder and the image folder is empty. Copied all the folders I have in Oricutron there, and I made it work...

Strange those folders are missing...

Cheers

Not strange, I removed them on purpose because I don't want to duplicate stuff in the OSDK. The ROM folder is one level up and shared with Euphoric, the image folder is not necessary. Now I did not check if disk configuration worked, only tape based stuff. Guess I need to check that.

About the old tools, well I sent a mail to Fabrice asking about native windows versions and got no answer so far.

Apparently I did a mistake when I packaged the version.
Believe me it worked, but since I test my version it creates TEMP and BUILD folders, so I need to cleanup, so probably I did something wrong there.

So what I fixed so far:
- Added the missing content of the image folder
- Fixed the bin/execute.bat to make it remember the starting directory (signaled by Woodmaster)

I tried all my samples, they all run fine, don't signal any problem with the roms, I checked with Skool Daze on the SVN, it's working well (just used one of the osdk_execute.bat from the %osdk%/sample folder)