101

(54 odpowiedzi, napisanych Fabryka - 8bit)

SIDE3 loader already has malware detection which no-one commented on, which suggests no-one even tried to run the malicious software in the first place. LOL.

102

(14 odpowiedzi, napisanych Sprzęt - 8bit)

_tzok_ napisał/a:

The key may be the difference in the reset circuitry in the XL and in the XE. In the XL the reset pulse is active as long, as you keep the Reset button pressed (it has some debouncing, but is prone to produce a pack of spikes on the reset line). In the XE pressing a Reset button, produces a single reset pulse of a constant duration (no matter how long you press the Reset button).

Yes: this was found to be a problem with U1MB too on some 1200XLs, but the solution (a cap on RST) did not alleviate the Rapidus issue. It seems highly likely that the problem is somehow reset-related, of course.

perinoid napisał/a:

And I have it installed in an XE, not in an XL machine.

Yes: I was initially reminded that the device was intended for XE machines, but then an adapter was produced for XLs. Go figure. It's 100 per cent likely that the thing was tested in XEs during development (albeit not with U1MB).

103

(14 odpowiedzi, napisanych Sprzęt - 8bit)

kkrys napisał/a:

Z tego co widziałem na Youtube to jest firmware 3.14 z obsługą Zośki.
Na oficjalnej stronie producenta nie wiem dlaczego jeszcze nie ma tego oprogramowania.
Może ktoś ma - niech się podzieli.


Dla PokeyMaxa:
https://www.youtube.com/watch?v=5iC2xVBD7d0
Proszę zerknąć w okolicach minuty: 38:36

Dla Sophia2:
https://www.youtube.com/watch?v=o_57LZJIDTI
minuta 6:39  oraz  8:09

The reason none of this is available yet is since both plugins require changes to the base firmware, and since the firmware targets several different platforms, the changes take time. Incognito is also getting plugins now (thus PokeyMAX and Sophia2 support, etc, but a CPLD update is needed), so I have my plate full coding this up without causing breakages. I'm about half way done now, and I have a machine sitting on the desk whose owner wants the plugins pre-installed on before it's returned, so believe me, I am as keen to see this completed as you are.

104

(14 odpowiedzi, napisanych Sprzęt - 8bit)

Oh yeah: look at the flawless 65C816 mode operation here:

https://youtu.be/EnfjxNqoZ7Y?t=1815

:D

105

(6 odpowiedzi, napisanych Miejsca w sieci)

krap napisał/a:

Rapidus dziala bardzo stabilnie z Ultimate, pod warunkiem ze nie jest to Ultimate z softem FJC.

Misleading. The the problems I observe are wholly reproducible with Candle's original firmware, and updating changes nothing, except revealing the fact that the VBXE core version is sometimes unreadable when Rapidus is present.

106

(10,045 odpowiedzi, napisanych Bałagan)

Pin napisał/a:

Spokojnie, epidemia się rozkręca. Uwierzysz w jej istnienie już niebawem. Jak większość niedowiarków ;)

Here in the UK they always say (from behind masks) 'just wait 2 weeks'. Still waiting since April. :)

107

(10,045 odpowiedzi, napisanych Bałagan)

Hmmm. Like the UK. The Public Health Act dates from 1984 (LOL), and is only now being used by the government to completely destroy the country.

108

(10,045 odpowiedzi, napisanych Bałagan)

Is this stuff true?

https://twitter.com/CatrionaColllns/sta ... 9611703297

109

(410 odpowiedzi, napisanych Fabryka - 8bit)

Jacques napisał/a:

Nie ma tu większego trolla niż Ty, mistrzu wsadzania kija w mrowisko, konfabulacji i uciekania od dyskusji szyderstwami z braku argumentów ;)
fjc niezorientowany - też dobre.
Medialność gry zweryfikuje sprzedaż.

Ad hominem insults are always the first resort of someone with no real arguments. Generally they expose their own character via their behaviour without any help from anyone else. :)

110

(410 odpowiedzi, napisanych Fabryka - 8bit)

_tzok_ napisał/a:

I've been confronted on the Forum with Lotharek and Candle and I found them reacting quite aggressively to any criticism of their products, and acting like they were the smartest and greatest people on the World, and everyone should love and adore them, and be thankful for their products.

No lies detected there. :D

flashjazzcat napisał/a:

This is called purism, I understand and respect that. This is retro stuff. The hardware is what it was back in the '80s. We can, and should, explore its abilities in software, but keep the hardware in its original form. If you like 16-bit CPUs, go for Atari ST or Amiga, or even RAPIDUS, but don't call RAPIDUS an Atari XE. It has nothing to do with Atari XE, except it uses its case, keyboard, and a (modified) system software. It can do things that real XE system could never do. It is really great, but it is no longer an Atari XE.

Yeah - I understand purism, but it's a perilous path. One would have to reject most of what's offered by a device like PokeyMAX as well, and I don't necessarily see such levels of ethical consistency.

111

(410 odpowiedzi, napisanych Fabryka - 8bit)

perinoid napisał/a:

I agree, that patching all U1MBs in the World is not possible. But, at the same time, it should be not that difficult to fix the firmware (if that's really a bug, which I have no idea about) and sell new cards already patched. This would make everyone happy - if there's a bug in fw, XXL should feel satisfied andpeople whould have rights to insist on patching his games to work on older, unpatched U1MBs.

I think Candle acknowledged the 'behaviour' of the hardware. You'll have to ask him why he didn't fix it in new devices. Wild guess? XXL's attitude has been so fucking obnoxious that the chance for a fix has been blown.

_tzok_ napisał/a:

Life is not simple... first step is to admit, that there is a bug.

Already done, AFAIK, by Candle. XXL admits no issue, however, with his own stuff, so has not even broached that first step.

So do you prefer simple, or fair solutions?

If you think it's fair to deliberately exploit a quirk of U1MB for no practical reason other than to make your software crash on the machine, I don't know what to say. I simply do not know what point is being made here, other than an ideological objection to a certain vendor or designer.

I have no doubts that, as the bug is known, it should be corrected. I'm aware that manufacturer/distributor may be afraid to admit, that there is a bug, because it could mean, that he had to correct it on his cost (at least for units, which are still within the warranty period) - by replacing or reprogramming the units.

Certainly I can't understand why one would not fix a bug unless the well had already been poisoned by politics, which I think is what happened here.

XXL seems to be a little too proud to give up, but so do the U1MB developers.

Note that the U1MB CPLD side of things has nothing to do with me. I consider exploitation of the issue to be incredibly childish, however.

I'm pretty sure, if the U1MB developers would publicly acknowledge that there is a bug in the U1MB, relesed a patched/corrected firmware, and started selling units with this new firmware, XXL would release a patch for his software to work with a stock/not pached U1MB. The war would be over.

Possible. All I know of XXL's personality is what he projects on forums. In my experience, anyone who will go to these lengths will be hard to appease. It is not without precedent, either. He advocates illegal OS entry points, seems to consider 'NEWDEV' an aftermarket invention, and has an ethical objection to 16-bit CPUs. I would personally not be prepared to pander to someone with such complex needs. :)

112

(410 odpowiedzi, napisanych Fabryka - 8bit)

_tzok_ napisał/a:

Don't you think, that both sides of the conflict are equally stubborn (you will probably deny, because you are one of the sides)? I don't think XXL even cares about correcting the bug, he just wants U1MB developers to admit, that it is a bug. You say "not worth bothering for one piece of software", so I bet he will release more software, which deliberately won't work with U1MB... just for his satisfaction, and to eradicate the argument about "one piece of software".

Simple question for you: which is easier? Distributing a JED file and asking every U1MB owner to purchase a Xilinx platform cable, download the Lab Tools software, make a suitable patch cable for the 2mm JTAG header, and flash the CPLD of their U1MB, or XXL changing his damn game?

I'm afraid I consider it a dick move to advocate the former solution when distributing actively maintained software. Not that XXL would say he advocates either solution, since it's clear to me that he is NOT LOOKING FOR A SOLUTION. He enjoys the problem too much.

113

(410 odpowiedzi, napisanych Fabryka - 8bit)

perf napisał/a:

Offtopic.  Ten błąd w U1Mb tkwi w firmware czy źle zaprojektowanej płytce ?  Bo niezrozumiałe dla mnie jest to też, że nie poprawiono tego. Wymaga zbyt dużego nakładu pracy ?

Not worth bothering with for the sake of one piece of software which only has an issue because of a pointless contrivance.

114

(90 odpowiedzi, napisanych Fabryka - 8bit)

Amazing quality!

AVG's SIDE emulation places the IDE registers at the exact same memory location as a real SIDE2 cart. So it's impossible to access both devices at the same time, no matter what changes are made to the driver.

116

(53 odpowiedzi, napisanych Fabryka - 8bit)

Cobol napisał/a:

Mogą, tylko trzeba zmienić numery partycji, żeby się nie pokrywały.

LSDEV and LSDSK tools (APT Toolkit ATR) can be useful here, since they display active device IDs and the location (i.e. host adapter) of all active partitions.

117

(53 odpowiedzi, napisanych Fabryka - 8bit)

pancio.net napisał/a:

Thanks FJC,
Tell me please, why I can't see SIDE2 as device to flash from computer equipped with U1MB... I tried with enabled/disabled Sparta on U1MB and SIDE2 board. I downloaded Side_Loader_v3.02 from your site. When I boot from ATR I see only message: "Waiting for SIDE2...". Finally, I updated only Sparta on SIDE2 because I can't do it from my 800XL with U1MB.

I flash SIDE2 on U1MB machines all the time. Secret is to ensure U1MB ROMs are not in the way. So: turn off PBI HDD and SDX in U1MB settings, put SIDE2 in SDX mode, and power-cycle machine. SDX will boot from SIDE2 and you can then flash both SDX ROM and loader ROM as you wish.

118

(53 odpowiedzi, napisanych Fabryka - 8bit)

UFLASH: Options -> Set SDX Size. If you have no need of the U1MB GOS, set SDX size to 320K. The flasher will then apply the 320K ROM without complaint.

As for SIDE: SDX is always 256KB.

Note SIDE driver is several generations old... a new one will be released in a matter of days now.

119

(16 odpowiedzi, napisanych Programowanie - 8 bit)

grzybson napisał/a:

Na razie ciekawie się zapowiada.
W kwestii GUI to chyba wzorcem jest to co zrobił FJC w fdisku do APT, uflash i innych.
Nie tylko menu, ale także listy, okienka dialogowe, przyciski, pola tekstowe, pola wyboru. W dodatku responsywne - działa w 40 i 80 kolumnach (VBXE lub soft. GR8).
Pytałem go nawet, czy kiedyś udostępni ten framework - owszem, jak będzie miał go kiedyś czas ogarnąć :/

Perhaps in the current circumstances, I will have time to address this request, finally. :)

Problem with my library is definitely code size, but once you start handling dialog boxes and file selectors with event-based callbacks (which is what is going on in FDISK, UFLASH, etc) and every control existing as a self-contained object, it takes a lot of code. GUIs are by their nature quite code-heavy.

120

(8 odpowiedzi, napisanych Software, Gry - 8bit)

http://www.mushca.com/f/atari/index.php?idx=A

Click 'Download All' on the right.

121

(1,755 odpowiedzi, napisanych Fabryka - 8bit)

Candle napisał/a:

dla wybranych komputerów zapewne

Be relieved if not among those selected. :)

122

(410 odpowiedzi, napisanych Fabryka - 8bit)

No more effort than the contrivances necessary to deliberately make software break on U1MB.

123

(410 odpowiedzi, napisanych Fabryka - 8bit)

voy napisał/a:

Widać pewną regularność; adres zmniejsza się o 4 bajty przy każdym kolejnym wystąpieniu. :)

Thanks! Heuristic anti-virus detection in next version of U1MB loader knows what to look for now. :D

124

(63 odpowiedzi, napisanych Software, Gry - 8bit)

Error code 132 ($84) means 'No device handler installed', so perhaps the SDX ROM is entirely corrupted at the moment. I have no idea; one would not normally see such an error message under any circumstances.

125

(63 odpowiedzi, napisanych Software, Gry - 8bit)

Download this: https://atari8.co.uk/wp-content/uploads ... 010819.zip

It has the latest SDX, loader, drivers, etc.