Nie jesteś zalogowany. Proszę się zalogować lub zarejestrować.
TURGEN 9.3.0 Kolejna wersja multiplatformowego narzędzia do zarządzania obrazami taśm.
SV 2024 WE - program imprezy Już za tydzień odbędzie się zimowa edycja Silly Venture
Nowa obudowa dla 800XL - zostało 36 dni Niewiele ponad miesiąc do końca kampanii.
Zmarł twórca języka BASIC Zmarł Thomas E. Kurtz twórca języka BASIC
Zmiana serwera atari.area Serwis przeszedł właśnie ważną aktualizację infrastruktury
atari.area forum » Posty przez flashjazzcat
Again: excellent work - many thanks for this.
Did you notice any instability on the machine? Other than that I am out of ideas too.
Yes. I'm sure. It worked. Besides, as I wrote before, VBXE J1 pin 8 is connected to P4 pin VB in U1MB, so I'm assuming it's connected properly.
...unless there's something else I should check...?
Nothing at all else to check, since it's worked on every other machine with VBXE in it. Of course a possibility for bugs exists, but I cannot imagine of what kind. Every other situation of this kind (in which old BIOS did what new BIOS cannot) eventually resolved itself in some hardware issue. What VBXE core are we using here? The BIOS attempts to map in the MEMAC_B window at $4000 to see if it replaces the Atari's base RAM. If RAM changes, we have a VBXE. If we can toggle presence of hardware registers by toggling VB pin, then we have a VBXE under control of the VB pin. It's that simple, so it's difficult to imagine why it would not work.
Besides, I did as advised Voy. Sflaszowałem U1MB to the old BIOS - could turn on and off VBXE. Of course, for checking I fired a couple of demos and games that require VBXE and working properly. Sflaszowałem again new bios and VBXE is again inactive and soft not to see him.
But Covox I can set enabled / disabled (?)
So - VBXE is enabled (therefore successfully detected), but cannot be switched off under software control. Same bits are toggled as before, so who knows.
Covox cannot be detected in software, so the option is always enabled. :)
Przed apdejtem w starym biosie VBXE było włączone i działało.
Are you sure of this? As I frequently write: old BIOS didn't care if there was a VBXE in the machine but would still let you choose $D6xx, $D7xx, or OFF for VBXE. If VBXE option doesn't show up in the new BIOS menu it means the decoding address is NOT under the control of the VB pin.
Once again, the old BIOS didn't know or care whether the VB pin was connected to anything, or if VBXE was connected to the wrong pin. So there's a good chance that things which seem not to work with the new BIOS never worked in the first place. I already saw this with numerous U-Switch/Stereo installations. "My stereo cannot be toggled with the new BIOS, but it worked before". Turns out it never worked in the first place, but the original BIOS gave no indication of any problem since it didn't test the hardware.
PBI BIOS displayed a version notice when SDX is enabled (on cold powerup when SDX bank = 0) from very early versions too.
Za jakiś czas może pojawi się tool diagnostyczny od FJC w którym może będzie to sprawdzane.
Ja nie umiem sprawdzić PBI - nie wiem co sprawdzać.
Memory and System->SpartaDOS X->Enabled
PBI BIOS Setup->PBI BIOS->Enabled
PBI BIOS Setup->Hard Disk->Enabled
Advanced Settings->PBI BIOS Notice->Enabled
Save and Exit->Save changes and boot
If you see "Ultimate PBI v.x.xx" at the top of the screen, you have the most recent CPLD.
What is suspicious about bootable ATRs? Is there something about them that you find untrustworthy? :D
Graphical OS is ROM-based, but you're free to ignore it if you want and use the space for a 320KB build of SDX. I'll refrain from further comparisons between a pre-emptively multi-tasking Graphical OS with overlapping windows, inter-process messaging, micro-kernel, etc, with TRS Desktop, since I doubt that will end well. Fortunately there's plenty of software available for those who appreciate nice colours. :)
@Yansen
In response to your question, you may read about GUI project here:
I'll make a ROM available for Ultimate shortly on my website - hopefully this weekend.
Meanwhile, hopefully GUI advertising won't send us too far off-topic.
http://atari8.co.uk/wp-content/uploads/ … a-BIOS.zip
Otwórz przeczytaj.
Panie.Potem oceniaj.
Please use versions posted in AA topic. I was asked to carefully document each fix in changelog, which I'm doing in recent versions. Website will be updated soon, but my second pair of hands is missing right now. ;)
Wersja 0.45 nie działała mi z SIO2BT, a dokładniej - nie resetowało "na zimno" z klawiatury SHIFT+RESET. Musiałem powrócić do wersji 0.24. Czy było coś z tym robione przy wyższych wersjach?
No clue what could be wrong with SIO2BT: check high-speed SIO settings, I guess. Shift+Reset problem is a known bug, since the function clashes with partition table re-read (also on Shift+Reset). Thanks for reminder: need to fix that.
Fixed.
Just received rather officious email from Konrad pointing out that ARC is missing. Pure human error: I must have removed it by accident using SDX Imaging tool while deleting all the MAN files.
Will fix later today.
It's possible to make a replacement using sheet aluminium, a laser printer, and a flat iron. I have done so before. If you can find no alternative, I can attempt to fabricate one when I find time.
Incognito build:
Ultimate update, including new loader:
http://atariage.com/forums/topic/240034 … try3389841
Incognito versions to follow.
So, can this be employed with VBXE to get a steady 640x400 16 colour display?
Thank you, but no: neither the Ultimate PBI BIOS nor SDX soft-driver for SIDE (nor any of the tools) require PBI.SYS. ;)
Thank you very much. ;)
Yes - it's unfinished so feel free not to leap out of your chair in excitement. :) The idea is to run GUI software, not the entire Atari back-catalogue of legacy titles. Think GEOS, SymbOS, etc. Of course this will rely on people writing software for it. If they do - great, if not - well, I will still have achieved the original objectives.
There's an existing thread for this, BTW:
Someone told me that there's an issue running the GUI demo and SDX together? GUI is 128KB and SDX is usually 256KB. GUI needs a 192KB SDX ROM (which is what's included on the complete ROM I published). If you happen to flash the standard 256KB SDX build to that ROM, problems will start. UFlash is able to change the expected size of SDX from 256KB to 192KB and back again, but unless you're able to create an SDX ROM of a suitable size, you'll have troubles. I'm told a future version of the SDX Imager will allow for seamless alteration of the SDX ROM size.
Incognito BIOS is new available in the same thread, or here:
Also, what is a software license of that BIOS?
Good question. I will let you know when I find out whether the firmware will end up pre-installed on a commercially marketed product. ;)
Please find a new beta main BIOS and PBI BIOS for the Ultimate 1MB:
http://atariage.com/forums/topic/240034 … incognito/
Incognito to follow shortly. A few features are incomplete but most things are 100 per cent working.
Hardware designer could not agree with author of SDX driver on how to decode RTC data. :)
I asked about some bugs which were reported before but the information I was given was difficult to understand even following translation and my general invitation for other users to test and report went by without a single response. Konrad and I debugged the partition editor quite extensively in previous years, so if new problems exist, I would be delighted to address them if I can be given detailed descriptions/screenshots of the issues and instructions on how to duplicate them. Beyond that I can do nothing at all, I'm afraid.
atari.area forum » Posty przez flashjazzcat
Wygenerowano w 0.018 sekund, wykonano 43 zapytań