Posts by Computeum@mastodon.bayern
(DIR) Post #AcyD2lpZAE5jCHiFv6 by Computeum@mastodon.bayern
2023-12-19T14:07:20Z
0 likes, 0 repeats
Wichtiger Meilenstein auf dem Weg zur Weltherrschaft erreicht:
(DIR) Post #AcyD2mzArzN4mNDRXE by Computeum@mastodon.bayern
2023-12-19T14:24:22Z
0 likes, 1 repeats
Mastodon scheint dabei deutlich besser auf #Retrocomputing zu reagieren als Bluesky. Beide Accounts sind ungefähr gleich alt (Bsky ~1 Monat, Mast <2 Wochen), und bringenden gleichen Original-Content. Trotzdem hats auf Mastodon schon die vierfache Anzahl an Followern.Freu!
(DIR) Post #AnFJYGJMlrrLTNDb9M by Computeum@mastodon.bayern
2024-10-21T23:14:59Z
0 likes, 0 repeats
@foone Dimilar calculations can be made for MOS' 6500 series.The most sold 6500 computer the C64 totalled 12.5 m according to Michael Steil. Even tripling that to account for floppy drives makes it less than 40 m. Let's make it 50 to include all other 6502 based Commodore.Famicom/NES alone sold 62m, SNES adding another 50m. Ataris 2600 only adds a mere 30m. So yes, chances are good that a 6500 in your house is a console ... except:WDC claims:"Annual volumes in the hundreds (100's) of millions of units keep adding in a significant way to the estimated shipped volumes of five (5) to ten (10) billion units."A number dwarfing all consoles combined.Bottom line, in average every human on this planes owns a 6500, withotu knowing about.
(DIR) Post #AngHW5oUyLdeLJ6Ydc by Computeum@mastodon.bayern
2024-11-03T23:29:23Z
0 likes, 0 repeats
@foone That time when the US closed their eyes to let their friends have bombs? The one that made others as well think it's fine to develop them? Yeah, and nowadays the boomerang gets another round by showing off how owning of them protects whatever they intend to do?Brave new world ...
(DIR) Post #AqysxTHyMuNLMuNeq0 by Computeum@mastodon.bayern
2025-02-10T16:29:53Z
0 likes, 0 repeats
@foone May I insert some really old news? DOS already parses the command line for you, putting up to two file names into prepared FCB. Add a zero byte and you'll fine to use stream calls - or stay with FCB handling.Using a 128 bye loop does no longer make a notable speed difference with today's machines and all their huge blocks and caching...https://archive.org/details/The_MS-DOS_Encyclopedia_Ray_Duncan/page/109/mode/1up?view=theaterAlso, doing it as a com program (tiny memory model) saves the need to copy segment registers or care for them at all. Plain code like on an 8 bit CPU :))
(DIR) Post #AqzjcaoOUxpgBpTVAm by Computeum@mastodon.bayern
2025-02-11T02:20:00Z
0 likes, 0 repeats
@foone True,but args are stored after the FCB prototypes. When DOS starts a program it fills FCB and args before executing. Thus even if the program does somehow changes its args, the FCB prototype should be unaffected. Anyway you got a working solution, so no need to change.
(DIR) Post #AwDvy1TeYWNJ9i4LOS by Computeum@mastodon.bayern
2025-07-17T12:04:50Z
0 likes, 0 repeats
@foone Not really Fx interrupts are reserved for user programs. A convention existing since the original PC. (GW)BASIC(A) for example uses F0. It was quite common to use one (or more) of them for internal function calls, shortening code and supporting modularisation. Also helpful when functions had to be exchanged depending on program state. That way no runtime checks for program states were needed. Just exchange the interrupt vector when the program state changes.
(DIR) Post #Awfa8WA2lT1aeNC0Yq by Computeum@mastodon.bayern
2025-07-30T20:12:05Z
0 likes, 0 repeats
@foone Oh, that's a nice thought :))Then again, XORing registers is an old assembly habit. It will produce on virtually all architectures the most compact code. Other ways may be as compact, but not shorter or faster.