Started by ikonsgr, 09:17, 01 December 20
0 Members and 1 Guest are viewing this topic.
Quote from: ikonsgr on 21:07, 10 January 22If you have a PIC programmer, try to reflash firmware.
Quote from: eto on 23:51, 11 January 22First time I power up the 464, it hangs after the copyright message (see image below). I click the reset button and then it fully boots. I can then click reset and every time it boots perfectly UNTIL I enter |USB. Once I do that and a reset will always fail. It always hangs after the copyright message like after the first boot. I have to turn off the computer and then start again.
Quote from: Mark_wllms on 11:06, 12 January 22I notice that the USIFAC needs a file extension to load a basic file, whereas unpatched AMSDOS will assume .BAS if not specified. For example if I have a file called "DISC.BAS", AMSDOS will normally accept Code Select ExpandRUN"DISC" whereas USIFAC will requireCode Select Expand RUN"DISC.BAS" to load it.
Quote from: shacpc on 00:59, 13 January 22Can someone add the FM file from the file manager without the initial question from the old device and directly start the file listing for a current one? thanks
Quote from: eto on 13:07, 13 January 22Hi @ikonsgr - so reflashing worked, but the 464 often hangs on boot and can sometimes not even be reset. I have to turn it off to make it work again. Any ideas if this can be resolved?
Quote from: eto on 21:42, 10 January 22A couple of other things that I recognized today with the 464 (I have another Usifac which still works):The filemanager has some issues with programs that have no extension and stops with an error in line 1. If not I often get a Syntax error or "File already open". A simple patch which creates a valid BASIC line will change that. Just add an ending ", a 0-byte and make sure the length of the line in &170 is set correctly. Even with this patch, the "File already open" error can still happen. E.g. Who dares wins fails after it loads another Basic file. Can this somehow be fixed?Would it be possible that the file manager continues to use the MODE that has been selected in the Basic part? The reason for this is, that on the original colour monitor (and even worse on the MP1/2 modulator) Mode 2 text is hard to read - and since it only uses 11 characters anyway, MODE1 or even 0 would not have any disadvantage and everybody could change the BASIC file based on individual preferences.
Quote from: ikonsgr on 20:09, 13 January 22One thing you can check is the psu you are using. Many times a power cable splitter or small psu can cause under voltage problems. Also, a bad edge connector contact can cause erratic behavior too.Anyway, with my CPC 464 everything works ok with rev6 firmware,never had such boot problems, so i suppose the problem doesn't have to do with firmware bug.Btw, i've upload again the last rev6 just to be sure it's the right one . Also, did you try to flash older firmware revisions to see if you get the same problem?
Quote from: eto on 20:39, 13 January 22I've checked WHO DARES WINS II, indeed the basic loader program has a run"loader command when the real file is "loader.bas". As i explained, with BAS files you have to mentions the extension in order to load it, so you can simply add .bas extension on the last command of basic listing, and then save the file, from now on it should work ok
rootdir: call check_usb_en ret z ld bc,&fbd0 call usb_cmd3 ld a,&2f out (c),a ld a,"/" out (c),a call usb_cmd2 ld a,&32 call usb_cmd4 cp &41 jp nz,error_ucd inc c ld a,53 ;set pic's path buffer to 0 out (c),a ret
Quote from: Fran123 on 12:39, 26 January 22HelloI did a launcher for UsifacII.You can test the project in https://github.com/gallegux/menusi
Quote from: issalig on 00:01, 02 February 22- boot a rom/sna when pressing a button, for example boot the one in the usb unit called autoboot.rom (maybe it could be used swap button or other free pin)
Quote from: issalig on 00:01, 02 February 22- add a rotary enconder and a screen like in a gotek (not so urgent and not sure about if enough free pins for screen and encoder)
Quote from: issalig on 00:01, 02 February 22- tutorial about usifac architecture and building instructions (I started a document but it is not still finished)
Quote from: Fran123 on 10:46, 02 February 22Hello,The code will be open when I consider that the project is finished, for now I would like to add a few things.On the other hand, I think that the code must be of quality to be published, I would not like you to laugh at what I write.
Quote from: Fran123 on 22:27, 03 February 22none shows the Usifac II Enganged message at boot up
Quote from: ikonsgr on 20:09, 13 January 22Anyway, with my CPC 464 everything works ok with rev6 firmware,never had such boot problems, so i suppose the problem doesn't have to do with firmware bug.
Quote from: eto on 23:43, 03 February 22This happened to me too several times. Seems Usifac easily "forgets" its ROM number and you have to assign a new one. Try "out &FBD2,5" on basic prompt, and then reset. If that doesn't help, you might need to reprogram it (happened once to me).
Page created in 0.111 seconds with 52 queries.