Jump to content
IGNORED

U1MB, Incognito, SIDE2, SIDE3, 1088XEL/XLD Firmware 4.0 Released


Recommended Posts

35 minutes ago, Level42 said:

Unrelated: I wanted to run the Prozac Dream demo (https://www.pouet.net/prod.php?which=68622) but the XEX file goes to a black-screen when trying to run it from SIDE3.

This XEX works without any special settings (i.e. PBI HDD on or off), so if it crashes, you have other issues.

Link to comment
Share on other sites

42 minutes ago, flashjazzcat said:

Did you update the PBI BIOS as well? If not, you'll have the SIDE/SIDE2 PBI BIOS uselessly polling for the CF card before the loader starts up and before the OS finishes initialising. That'll take 4-5 seconds. ;)

 

 

I didn't and sure enough doing that fixed it :)

  • Like 1
Link to comment
Share on other sites

1 hour ago, Beeblebrox said:

The 74F08 chip is dirt cheap and has solved a lot of issues for me. Well worth it, as is running a modern usb 5v 3a power supply. 

Ordered 2 74F08's from Germany for just 5,57 Euro incl. Shipping from Germany (http://www.kessler-electronic.de/Halbleiter/integrierte_Schaltkreise/digital/74_F/74_F_08_i458_3420_0.htm)

 

It's U7 on the 600XL....at least that's the only 74LS08 I can find on it :D


If it's not fixing anything, it's not making anything worse either I guess :)

 

Link to comment
Share on other sites

1 hour ago, flashjazzcat said:

This XEX works without any special settings (i.e. PBI HDD on or off), so if it crashes, you have other issues.

Doesn't want to run, either in NTSC or PAL setting. 
Did get the demo (or it's preview ?) to run from a large Silly Venture ATR file though...so it's not the demo itself.....

Let's try downloading it from somewhere else...

 

My machine is full of stuff but hasn't let me down so far, not even with PoP ;)

 

Link to comment
Share on other sites

1 minute ago, Level42 said:

If it's not fixing anything, it's not making anything worse either I guess :)

Hopefully not, but it's never a happy day when the source of the buffered O2 signal on the Atari has to be modified to make it work with something, since there's a slight possibility that doing so will make the machine stop working with something else.

 

This fix is so determinate and effective, however, that hopefully it will result in a fix on the cartridge which makes it unnecessary.

  • Like 2
Link to comment
Share on other sites

6 hours ago, mytek said:

It should just run directly from any DOS.

 

Yeah I know but I need to put it in an ATR to be able to load it from SIDE3 or through SIO2PC using Redpeqt, right ? Haven't created an ATR and added files to one on my Mac in ages....

Link to comment
Share on other sites

10 minutes ago, Level42 said:

Yeah I know but I need to put it in an ATR to be able to load it from SIDE3 or through SIO2PC using Redpeqt, right ? Haven't created an ATR and added files to one on my Mac in ages....

Yes for SIO2PC you will need it in an ATR container, but not for either either SIDE3 or SIDE2 (or the numerous other multi-carts out there). Files with the COM or XEX ext will run directly from the SIDE Loader. Just copy them into a FAT32 formatted card and they'll appear in the Loader ready to run.

Link to comment
Share on other sites

You don't need an ATR at all. If you have SIO2PC and RespeQt, set up a virtual folder as a DOS 2.x or SDX volume in an unused drive number. Drop whatever you need into said folder and then use the SDX COPY command to copy the file into a 512bps SDFS formatted APT partition. Once that's done, make the partition the default by typing its drive number at the SDX command prompt, then type RWCRC. Done.

  • Like 1
Link to comment
Share on other sites

4 minutes ago, mytek said:

Files with the COM or XEX ext will run directly from the SIDE Loader. Just copy them into a FAT32 formatted card and they'll appear in the Loader ready to run.

This isn't going to be much use here since RWCRC writes a large CRC file to the HDD and then reads it back again. When the SIDE3 loader is capable of writing to the FAT (soon), RWCRC will work, but right now it will immediately trigger a "no function in device handler" error if you try to run it directly from the loader.

  • Like 1
Link to comment
Share on other sites

Hold your horses my friend....

I'm trying to get "a 512bps SDFS formatted APT partition" :)

But I need to honor your incredible work on the U1MB firmware manual and f-ing RTFM before asking the stuff you already explained :) (Printing 91 pages as we speak....handier to have it on paper next to the 600XL).

Guess I'll need some SpartaDOS manual too. It's about time I learn to use it for more than just flashing U1MB :D

Thanks for your patience with me :) 

  • Like 3
  • Haha 1
Link to comment
Share on other sites

I've got a bit of a problem.

 

I flashed the entire ROM using 'U1MBS3.ROM', which went fine, SIDE3 is detected and boots as normal, but I have the 'VXS3STCO' plugin installed - Which is no good as I have Sophia 2.

 

I try to flash the 'SOS3P2.ROM' to the 'BIOS Plugin' slot and I get the error 'File too large: Expected 1KB'. What am I missing here?

 

s4yiWAQ.jpg

 

6mcyZID.jpg

 

EDIT: This doesn't look right?

 

V1TRWpJ.jpg

Edited by Mazzspeed
Link to comment
Share on other sites

Tragedy averted...

 

I started the whole process again from scratch. Reflashed the entire ROM with 'U1MBS3', rebooted and flashed the plugin slot with 'SOS3P2.ROM', which seemed to flash and verify just fine. Booted back into the U1MB BIOS screen and checked, everything is good now.

 

How odd...?

Link to comment
Share on other sites

5 hours ago, Mazzspeed said:

How odd...?

You upgraded from firmware 3.x to firmware 4.x without a power-cycle. Technically, the fact UFLASH didn't notice the transition in plugin size from 1K to 2K is a bug, but it is not a good idea to jump firmware generations and then start applying plugins without power-cycling first, since the entire configuration layout changed. If you happened to have the PBI BIOS enabled during the update, the whole SIO subsystem will be invalidated as well when moving from 3.x to 4.x.

 

I will fix this, anyway, but that appears to be your problem. I could reproduce it only by starting with firmware 3.x, turning off the PBI BIOS, updating to 4.x, and then attempting to flash a plugin without power cycling the computer.

 

Link to comment
Share on other sites

4 minutes ago, flashjazzcat said:

You upgraded from firmware 3.x to firmware 4.x without a power-cycle. Technically, the fact UFLASH didn't notice the transition in plugin size from 1K to 2K is a bug, but it is not a good idea to jump firmware generations and then start applying plugins without power-cycling first, since the entire configuration layout changed. If you happened to have the PBI BIOS enabled during the update, the whole SIO subsystem will be invalidated as well when moving from 3.x to 4.x.

 

I will fix this, anyway, but that appears to be your problem. I could reproduce it only by starting with firmware 3.x, turning off the PBI BIOS, updating to 4.x, and then attempting to flash a plugin without power cycling the computer.

 

I was already on firmware 4.0, upgrading to 4.05 - I honestly can't remember if I power cycled between the firmware update and the plugin reflash.

 

Point taken, for now on I'll be sure to power cycle between firmware flashing and plugin flashing. Cheers FJC.

Link to comment
Share on other sites

3 minutes ago, Mazzspeed said:

I was already on firmware 4.0, upgrading to 4.05

UFLASH clearly thought differently. It checks the firmware revision (apparently only when probing the hardware for the first time, forgetting to do so after a BIOS update) and if it's >=4.0, it expects a 2K plugin. Your photo showed UFLASH expecting a 1K plugin at the older plugin address. I don't know how you managed to accomplish this, but there is no determinate explanation for it other than the scenario I have outlined, or by using an old version of UFLASH which has no knowledge of the 2K plugins.

Edited by flashjazzcat
  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...