ULIfAC:Usb Mass storage,WiFi, 512KB Ram/32XROM Board/256K Ram+16X Rom Board!

[MoiCJarod]

I downloaded somewhere as a zip file.
It works very well. I dont know what binary or cpr.
Attached the zip file.
[/url][/img]

[/url][/img]

Edit: I also ad some ss but i cant see them. Maybe it's because we have the best internet connection in the world

Ok, working on my CPC 464 on 256k+ 16x rom. And wow ... hard to play ...

And ... what is "ss" ?

[MoiCJarod]

(btw all of this info is mentioned in user's guide too: https://www.dropbox.com/scl/fi/x1cad8kzzsugn1razoy74/ULIFAC-User-Guide_v5.pdf?rlkey=x14349neqsmxum5xmhuwyo82f&dl=0 )

Of course, I should have rtfm ... 

[unay]

I downloaded somewhere as a zip file.
It works very well. I dont know what binary or cpr.
Attached the zip file.
[/url][/img]

[/url][/img]

Edit: I also ad some ss but i cant see them. Maybe it's because we have the best internet connection in the world

Ok, working on my CPC 464 on 256k+ 16x rom. And wow ... hard to play ...

And ... what is "ss" ?

Screen Shots, while loading and playing.
Maybe its my phone, tomorrow i'll try to edit on a computer.

[MoiCJarod]

Ok, I am again in a weird configuration ...

Config.txt enabled, I am in 256+16x Rom mode. Doing a |fm, selecting a dsk file, and then the computer reboots twice and some pixels are lighted on the screen, the CPC is hung. (same occur if I |mg, "....DSK" then |fdc).

Other thing : can't launch |rom rsx, temporary message shown : "No RAM/ROM board present, or switch to". 

[ikonsgr]

Config.txt enabled, I am in 256+16x Rom mode. Doing a |fm, selecting a dsk file, and then the computer reboots twice and some pixels are lighted on the screen, the CPC is hung. (same occur if I |mg, "....DSK" then |fdc).

Most probable this is a bad/copy protected dsk image. There is also a chance for this to be  a CP/M image, which usually executes directly by giving |CPM at prompt.
If you try to "CAT" such CP/M image, you might get the weird behavior you described.

Other thing : can't launch |rom rsx, temporary message shown : "No RAM/ROM board present, or switch to". 

Rom configuration utility works ONLY in default 512K Ram expansion mode (obviously because you can't change "on the fly" rom setup while roms are in use, as in Dual RAM/ROM or 32x Rom board modes!). Again ,this is mentioned in User's Guide too 

[ikonsgr]

Hmmm, this begins to be very interested:  "officially"  cpr cartridge rom games were meant to be for Amstrad PLUS models only, but as  some very skilled game developers seem to have a particular fond for using "roms only" , it's very satisfying that ULIfAC can load two of the most famous "cartridge rom only" games, that also work on Amstrad CPC: Alcon 2020 and Hyperdrive! 
I've also successfully load "Space moves" using a 512k cpr rom cartridge, although this is available in dsk format too...
Anyway, since now ULIfAC seem to be able to load cartridge games too, i'm thinking of developing a small windows utility that will take a cpr file as input and give you a folder with the BAS loader and roms in required format, ready to use!
This will make the hole procedure of trying cpr files with ULIfAC "piece of cake" for anyone! 

Btw, i wonder, apart from Alcon 2020 and Hyperdrive, are there any other "cartridge only" games that support Amstrad CPC too?...

[MoiCJarod]

Most probable this is a bad/copy protected dsk image. There is also a chance for this to be  a CP/M image, which usually executes directly by giving |CPM at prompt.
If you try to "CAT" such CP/M image, you might get the weird behavior you described.

It was dsk files that I mounted successfuly before ... maybe my usb stick that is slowly dying ? Well, I will see this tomorrow.

Anyway, since now ULIfAC seem to be able to load cartridge games too, i'm thinking of developing a small windows utility that will take a cpr file as input and give you a folder with the BAS loader and roms in required format, ready to use!

+1 

[eto]

I have iram640 which is onboard solution for ram. Ulifac is disable the iram ınfortunatly. Maybe @ikonsgr has solution for that...

What do you mean with ,,disable the iram"? The iram640 should never be disabled unless you are using the disable switch. 

It should have priority over any external RAM expansion.