76

(10,041 odpowiedzi, napisanych Bałagan)

If we want to empirically evaluate the perceived threat-level to the vast majority of the healthy population from COVID-19, we need look no further than the most senior members of the British government, who clearly did not perceive the virus as a serious threat as early as May 2020 (seven weeks into the first UK lockdown), when they hosted 'bring a bottle' parties (um... 'business meetings') at 10 Downing Street while Joe Average was prohibited by law from socialising with his friends and family, on pain of fines and criminal prosecution. Of course, anyone observant knew this at the time (even though revelations about said gatherings were only leaked in recent months); you need only watch Nancy Pelosi getting her hair done, government officials removing their masks as soon as they believed the cameras were off, the UK health secretary removing his mask as soon as he walked into 10 Downing Street, US Governors having illicit social gatherings, etc, way back at the height of the crisis.

While all this was going on, the Queen of England sat alone at her husband's funeral, and a man sat crying in the car park while his wife died in hospital.

Whether these well-timed 'leaks' are deliberate and designed to help change the narrative (the press now pivoting against lock-downs, suggesting T-cell immunity from the common cold might protect against COVID, downplaying the seriousness of Omicron, etc) I do not know, but many observers seem locked in a state of hypnosis, still complaining that the people who 'broke the rules' should be punished for breaking the rules. Apologists maintain that 'it was a mistake', and 'we're deeply sorry', but many people are completely missing the point. If the people who were the architects of the pandemic response clearly and consistently ignored the restrictions they placed on the rest of the population, this should tell us one thing and one thing only: that they did not perceive the virus as a serious threat to themselves or their families.

Of course, it will take months or years for this to 'sink in' with many people the function of whose daily existence for the past twenty-two months has been to advertise the existential threat to healthy adults and children (remembering that 75 per cent of those dying from or with COVID had four co-morbidities), shout 'govern me harder, daddy!', wear ten masks, and eagerly take any injection offered them on condition that they are allowed to work or go on holiday. And I can hardly blame them at all, because they were terrorised by state-manipulated media to the point at which they will have to completely realign their worldview in order to comprehend what actually happened. And many people were simply obliged to go with the flow for the sake of their livelihood.

And yes: trying to vaccinate your way out of a pandemic was regarded as a dumb idea until about a year ago, when... um... 'the science changed'.

Good thread, anyway.

77

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

bugz_ napisał/a:

I was able to reproduce issue originally posted by @Pin and can give you some more insights. MBR gets corrupted when final number of created partitions is exactly 16, 47, 78 etc. Partition size doesn't matter.

This is most useful information; I was trying to recognise some such pattern yesterday when testing, and I was able to corrupt the MBR when the number of partitions was exactly 78. But if I used 'fill/divide' to simply create 100 partitions, there was no problem at all. So it seems that the TOTAL number of partitions must equal one of these 'magic' values, exactly as you say.

This patterns seems to correlate with maximum number of partitions which one can create in one sector. First number seems to not match my theory but first APT partition has also 15 mapping slots which makes theory plausible.

Good observation. What with my distracted mental state recently, I spent a few seconds trying to correlate the numbers with the various sector boundaries in the APT chain, but totally forgot while doing so that sector 1 of the chain is special, in that it contains the mapping slots in the first 256 bytes, and therefore only 16 partition table entries (in the upper half). Now, it starts to make sense.

I read APT_spec and create small python script for disk analysis if you would be interested. It helped me identify that issue.
If you would need any help on that just ping me.

Again - this would be most helpful. I may well get in touch, although I did (years ago) write an A8-based utility which dumps the entire APT record chain with absolute sector numbers, etc. It might be a lot more expedient to use a PC-hosted tool, however. Naturally the partition editor is burdened with complexity and eligible for many re-writes when I get time (I now dislike the mandate that all partitions are kept contiguous), and I have not done any serious work on it for some years.

The other interesting thing is that we had an issue just like this in the past, and I addressed it, fixed the primary fault, but yet a problem persists (coming to light literally years later). In any case, thanks to your analysis, I have some clues now. :)

78

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

Yeah: this is definitely a bug. I'll look into it when I get time. Thanks for flagging it up.

79

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

We can see quite well how what's shown in the video works. :) If this was empirically the only/best way of doing things, every DOS would work this way, but it does not. Offloading everything to the peripheral is all nice and good, but I don't really see what it proves, or what my 'whims' have to do with it. All systems have to be 'designed' in some way, and the programmer has to make decisions. XBIOS chose to use a completely proprietary API. I assume that was one of your 'whims'. :)

In short: I answered your question regarding long filenames. A follow-up lecture or debate is completely redundant. Imitation is the sincerest form of flattery, however. I appreciate that. :D

80

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

FMS in the loader handles long filenames, CIO DOS handles short filenames. You can access the files with long names via the short alias. Long filename handling is extremely code and buffer heavy, and there would be no hope of housing such an FMS in 5K... unless your AVR/MCU is doing all the work and the software on the Atari side is just being handed long filenames via the API.

It would be largely pointless anyway, given the fact almost all software which works with DOS expects 8.3 filenames.

81

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

Getting into the SIDE3 Loader without disturbing the underlying application (providing the application is reset protected) is almost certainly doable, given time. The latest (unreleased) version of the SIDE3 Loader can be run interactively from the SDX prompt as well, if that's useful.

There is no IRQ signal on the cart connector, meanwhile, so you will never trigger an IRQ with a button the way it can be done with PBI devices. Such a facility is of rather limited use anyway if the running application happens to turn interrupts off.

82

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

Advertising AVG in the SIDE thread. Classy move.

83

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

Santyago napisał/a:

No tak, piszę, że czarny ekran mam na wyjściu composite / svideo - nie na dvi :)

Utterly bizarre. Quite the opposite to what I expected, in fact. Perhaps Simius needs to be involved in the investigation.

84

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

Check the legacy video to see if it actually made it into the BIOS menu. I've seen strange black-screens on the DVI output from time to time and would like to investigate it further.

85

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

SDX on the SIDE3 cart serves no purpose whatsoever when U1MB is present and the PBI HDD is enabled. The purpose of this config is to use the cartridge solely for mass storage and cartridge loading. The exact same version of SDX is right on the U1MB and you should use this one. The SIDE2/SIDE3 driver cannot process CONFIG.SYS, because the default CONFIG.SYS (on the CAR: device of the cart's SDX ROM) installs the driver which allows access to the HDD.

The MERGE command (as described above) is a good workaround for CONFIG.SYS amendments, but as said: you need not worry about this on an U1MB machine.

86

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

Auto-translation certainly makes your post appear semi-literate, but since I do not speak Polish, I cannot say if this is down to the failings of the translator, of it is simply a faithful representation of the character of the original writings.

I think I bet on the latter ;-)

I see: 'Muh... AVG... muh... XEP80... blah-blah... system graphics routines'.

87

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

How can I 'troll' people by attempting to deflect irrelavant discussions in my own thread? I don't give a f**k whether people use XBIOS for their games or not, but it would be helpful if the author would include a caveat for 'Clueless users' (© Rensoup) pointing out that the software will not work with ubiquitous storage solutions. This way, I would never even have to comment on the matter again.

88

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

zbyti napisał/a:

Faktycznie, wygląda to bardziej na sprawę osobistą niż techniczną.

I don't know the guy from Adam, but I create one thread a year and he was shitting all over it. I'm sure he's a lovely person but he decided to whine loudly about off-topic things.

89

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

alex napisał/a:

Hmmm... How about product description?
"HDD emulation with U1MB    - yes"
"SIDE2 emulation (compatible with U1MB and SpartaDOS X)"
(source - https://avgcart.tmp.sk/)

Yeah? And? Try mounting a cartridge from the SIDE2 loader in SIDE2 emulation mode with AVG. Or try using the U1MB PBI HDD after mounting a cartridge using the AVG menu. Not possible. SIDE3 with U1MB allows cart emulation, hard disk partitions and ATRs all working at the same time, all selectable from the same loader.

90

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

perinoid napisał/a:

Robiłem mało miarodajny test i wyszło mi, że Side3 jest ciut wolniejszy jeśli chodzi o pracę jako dysk twardy (pod SDX). Ale karty są inne, dlatego test traktuję jako nie do końca miarodajny.

There is a lot of variation in speed when it comes to SD cards, and this must be down to access times. The Sony 8GB card I used a lot during development was a lot slower than - for example - a 32GB SanDisk card I tried later on during testing. The SanDisk could manage 64KB/s reads in RWTEST and 55KB/s writes no problem at all, which matches typical CF card speeds with SIDE2. YMMV.

alex napisał/a:

Rysiu, ja też bym brał AVG Cart. Lepszy i tańszy :)

AVG may have the edge as a stand-alone cart if you want ATR support and wire up the built-in SIO device. But if you're an U1MB owner (as Ryszard appears to be), you will miss out, because AVG cannot emulate SIDE2 and run carts at the same time. SIDE3 allows cart emulation, HDD partitions, and ATR mounting all in one device with U1MB, all from the same loader menu. OSS Action! with hard disk partitions and bootable ATRs? No problem. Sure: AVG is cheaper and the SIO emulation is pretty killer if you want to move the cart from one machine to another, but for those already invested in U1MB or thinking of purchasing U1MB, SIDE3 is a more integrated solution.

91

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

UnDead napisał/a:

@perinoid z tego co widzę, owszem, ma - w przypadku wsparcia dla ATR, bo to cudo wkopiowuje sobie po prostu obraz ATR do swojego RAMu i dalej działa jak kart... Oczywiście nie analizowałem samego kodu i nie mam zielonego pojęcia, dlaczego (skoro ma 2MB SRAM na pokładzie) może wczytać tylko 180K ATR-a itd. Wydaje mi się, że są tu osoby z o wiele większą wiedzą na ten temat...

The reason disk images are limited to 180K without U1MB support is that I just decided to chop the available SRAM into four (minus the overhead for 1MB cart emulation plus what the loader needs for directory storage) and allocate the same fixed 180K to each disk image. If there is no need for four images (perhaps two would suffice), the supported size could be doubled. Or I could implement a more sophisticated memory allocation scheme if there is actually any call for it, and it justifies the amount of effort involved. I ported the complete SIO mounting API from the U1MB PBI BIOS to the SIDE3 loader in order to minimise complexity (the loader 'thinks' it is calling the SIO with the same parameters as it would use when interfacing with U1MB).

92

(54 odpowiedzi, napisanych Fabryka - 8bit)

There's nothing to see. It's external in the sense it's not installed in any computer. :) It was funnier in the pub.

93

(54 odpowiedzi, napisanych Fabryka - 8bit)

mono napisał/a:

Szkoda, że z VBXE tak się nie da :/ Albo z Rapidusem.

I already have an external Rapidus here. Standard version, but left in the drawer.

94

(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.

95

(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).

96

(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.

97

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

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

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

:D

98

(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.

99

(10,041 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. :)

100

(10,041 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.