Recent Posts

Pages: Next page
Programming / Re: Amstrad Github? or where to share the code?
« Last post by zhulien on Today at 07:56 »
Actually public domain software does NOT require the source code to be provided, that is a fallacy likely related to closed source (which is also not the same as closed software).

You can very well explain the process to create the public domain software without source code if it was created without source... such as the stream of hex numbers to type into a file.  Of course not much software is created these day like this, but it doesn't exclude that - as it is exactly how you need to program something like... let's say... a computer which only has a hex keypad.
Programming / Re: Amstrad Github? or where to share the code?
« Last post by pelrun on Today at 07:08 »
> sufficient in Australia

Dunno where you get that from, thanks to the Berne Convention we're also subject to how other countries interpret copyright law. The person using your code needs a clearly stated license saying they can do so, or they put themselves at significant legal risk. Nothing stops an author from deciding to revoke the invalid "public domain" declaration at any time and launching legal action against a prior user of the code.

GitHub actually provides a license that provides the same permissions as "public domain", which you would have found if you'd looked:

Note: this is for using *code*. You're conflating that with using *software*, which generally means a compiled executable which as you say doesn't need a license to use, but also doesn't support derivative works.
Applications / Re: File tools: even jobs.
« Last post by m_dr_m on Today at 05:24 »
Now I'm curious about your opinions, even if I may not expect too much of excitement.
Great idea. We gathered some ideas for ANA OroboroS project (kickass name),  @zhulien already has done some design investigation for shared RAM and unified driver interface.
This could and should be done incrementally, to solve some concrete problems. For instance, Orgams already use RAM persistance (sources still available across reset, with checksum verification). But Parados drive-tool would trash the memory (destructive RAM check, what a pity). Common routines to get the RAM amount and reserve a bank would be a good start.

Would be happy to give some feedback **before** it's too late.
changes like this really mean you haven't got a CPC anymore

That depends on which bit is the CPC to you.  If you change your 3" drive to a Gotek, is it a CPC?  If you change your keyboard to a PS2 keyboard, is it a CPC?  If you change everything to a JustCPC, is it a CPC?  I guess my PC is not a PC anymore and my Amiga is not an Amiga anymore and my CPC is not a CPC anymore... because they are enhanced.
Applications / Re: File tools: even jobs.
« Last post by m_dr_m on Today at 05:15 »
A bug? No, there is no bug at all.
Not saying that UnIdOs is bugged (well, i also said that, but I was young and rebellious).
In my book, that is not the best design choice.

Applications should avoid manual path handling and always rely on DOS layer for this purpose
Sure, it's nice to hide complexity and propose a well designed API.
Yet, as a mathematician, I love patterns and isomorphisms (even if I don't proclaim that in my dating profile). Being able to be form paths by simple concatenation is a nice property. That's a bit sad to lose it.
Also, complexity is not hidden after all, more often than not we manipulate path by hand (that is, non-programmatically). Then we are likely to face ambiguity and confusion before this non-standard choice.

Finally, all of this was not decided for UniDOS itself, it was already used by the Tape2HD interface of ACE CPC Emulator about ten years ago.
Yep, an amiga program interfacing an amiga filesystem.
Programming / Re: Amstrad Github? or where to share the code?
« Last post by zhulien on Today at 02:30 »
The car/drivers license example does not really fit. That would be, if Github would force anyone who gets the source code to proof, that they can code. It's more the equivalent if you rent a car during your holidays and confirm that you will not go offroad or to restricted areas. You still obviously can do that, but if anything happens, you will be in trouble.

If you want anyone to use your software without a license, you have to have a license that supports this. Sounds ironic, but you forget, that there are laws that otherwise, depending on your country, will apply which would prevent exactly that, what you want. Copyright, Urheberrecht, whatever... You need a license to make clear that these laws do not apply to your code. Without specifying a license, whoever is reusing your code, would immediately violate these laws if he doesn't reach out to receive your individual permission (which is also kind of a license). The lack of licenses was exactly the problem of "Public Domain". It's simply not defined what it means. Is it allowed to sell, modify, redistribute? Add a license to your code, and everybody can see what is permitted. The MIT license is, what I think is most closely to what I understand to be "Public Domain".

There are no laws in Australia that require you to have a licence for software.  Putting it into the public domain and stating so with the software is not a licence but sufficient in Australia.  MIT is a licence, Public Domain is not.  GIT supports MIT but not Public Domain.

Strange, on my amstrad works fine. Check again your listing maybe you have some type error somewhere.
What exactly you mean by copy files inside usb? Move a file to another directory perhaps?
Anyway,i manage to modify the disk2image routine to an rsx command (|DISK,"name") which also creates a dsk image file, without needing a pre-existed one  ;D
I'll see to make it as a stand alone program and upload it in the weekend.
What tools do you use to change the key's? Still only a hex tool?
I thought key control of the game that was the main problem.
Use the non-compressed tape version.
I have almost solved the graphics problem.
Very clever. Whilst it would be nice on the CPC to have something similar, the main use would be for patched games - Sentinel, Freescape games, and so on, that could be patched "easily" enough to make use of such a speed up. Otherwise it would be so rare that nobody would write for it.

But I would like it in the CPC FPGA cores for mister, etc - assuming one day I get such a thing.
Note that changes like this really mean you haven't got a CPC anymore, just something that Amstrad should have done with the CPC Plus range but didn't.

I don't know how viable it would be to take one of the FPGA Z80 implementations, and stick it on a Z80 compatible form factor, at 4MHz, looking to the rest of the system like a normal Z80 timing-wise, but internally redesigned with a full 16-bit single-cycle ALU (to speed up processing) and instruction cache (to reduce issues with slow main memory access, sorry games that use self-modifying code). It might end up looking more like an R800.

Most graphics routines use the 16-bit register pairs and instructions, so this would be the single best way to speed up the performance - although limited by the main memory access times for writes.

I've done something like this for the BBC Micro - a board which plugs into the 6502 socket and replaces the CPU with a WDC65816 (6502 compatible with a 16b mode) and a fast 512KByte RAM with a CPLD to implement all caching and memory remapping logic.

It works well, slowing down for access to host resources but otherwise running at full speed asynchronously to the host computer. The latest incarnation is stable at around 16MHz. Quite how much of that speed up you get is very dependent on how often you write to screen RAM (slow writes) and other peripheral locations. For BASIC programs like the sphere demo you really do get most of it (~7x), but for hugely IO bound tasks like being a host to an Acorn 2nd Processor the speed up might be just 50% or so. And of course it's no use at all for most games which will just run too fast, but things like chess programs or adventure games might appreciate the speed boost.

The main thing is though that it still feels like a BBC Micro. It's highly compatible. It's faster. It has more memory for BASIC (shadow mode) - not such an issue on the CPC. It offers more ROM slots and sideways RAM. Essentially though it does still feel like a Beeb.

I wonder about doing something similar for the CPC, but again this kind of acceleration is probably of no interest to gamers since you'd end up disabling it most of the time. Great for CP/M and BASIC programming of course but I feel the target market is shrinking there ...

Pages: Next page