Piotr D. Kaczorowski
-
Posts
338 -
Joined
-
Last visited
Content Type
Profiles
Forums
Blogs
Gallery
Events
Store
Posts posted by Piotr D. Kaczorowski
-
-
Alright. Everything is going great, and we can probably refine and add new systems. The only drawback right now is that it simply doesn't work for me
- Input/Output Error 5. So, we need to determine the next steps. Do you have any ideas, or should I try to set up a tunnel and expose the host so you can check it, or should I add debugging in my free time and see what's going on?
-
34 minutes ago, Wrathchild said:
Probably better to talk in terms of features you'd like the Pico to support
Electronics is my focus.
-
6 minutes ago, Wrathchild said:
Completely different processors:
https://github.com/robinhedwards/UltimateCart
https://github.com/robinhedwards/UnoCartSure.. But A8Pico is based on RP2040 Pico purple clone. Is there any chance to port UltimateCart on such platform ?
-
How much does the hardware handling differ between UnoCart and UltimateCart? Could UltimateCart be made based on Pico?
-
A bit off-topic, but I've noticed that UltimateCart has returned to the market.
-
I know this is probably not what you'd like to hear, but as you know, many of us simply have a second Atari in either PAL or NTSC version. It might be hard to expect demos to account for the 50/60Hz versions as well as NTSC Artifacting (probably in two versions) and PAL Blending. There's a clear reluctance even at the stage of porting PAL games for NTSC systems.
-
1
-
1
-
-
A small request that will enable debugging under different systems with different versions of libraries. It shouldn't be too complicated and probably won't take much time, but it can help many times.
Please consider to add a "--dummy" option, e.g. "atrfs --dummy /mnt/atrdisk"?
The goal is to test-install a virtual ATR, which will return a short list of files, or for files, it will return the content "hello world", allow copying a file to the virtual disk - but only this will create a file that will contain "hello world". Such a thing will make it easier to add DEBUG and determine incompatibility with a given system or fuse library.
In the future, the fs layer could be divided into two layers. The lower one would simply work generically, and the higher one, interfacing with the FS library, would have all the options/pragmas related to a specific version of fuse or another library that would allow the implementation of a virtual FS.
I know that, unfortunately, this would require a thorough rewrite, as it's a change at the design level.
-
A use case consistent for many years with Unix systems:
mount_atr montezuma.atr /mnt/atrdisk1
So, mount_atr corresponds to atrfs, but in principle, you shouldn't add --name. Personally, I would replace name with "--src", although this would mean that when creating disks it should be "--dst". However, if a token in the arguments has the ".atr" extension, it should be treated as "--name=....atr".
All in all, it's just a cosmetic touch at the end, once other more important issues are resolved.
-
5 hours ago, x=usr(1536) said:
My suspicions that this is an Aliexpress converter in different clothing are strengthening. No definitive proof is possible without comparing the internals of both and Apollo and Aliexpress unit, but the following image (taken from https://www.aliexpress.us/item/3256805525735745.html) is interesting:
Omit the AV/SP/PC, PIP, and MENU buttons and the RESET, MODE, and P.P buttons appear in the same sequence on the Apollo; there's even a gap in-between MODE and P.P where the MENU button doesn't appear on the Apollo. The button functions also line up, at least based on the descriptions of what they do. Finally, the SVGA port appears to be in the exact same orientation and location on both in relation to the buttons.
For $5, I decided to splurge and ordered one. It'll be here in two to three weeks. If anyone has one of the Apollo converters and is willing to open it up, I'd love to do a comparison once the Aliexpress unit gets here.
I had something like that in the Atari set when I bought it again in 2020 after many years. You can safely throw it away. The image quality is terrible.
-
1
-
-
I've checked the sources. I'll likely add more DEBUGs to the code either tomorrow or on Friday to identify the issue.
-
8 minutes ago, pcrow said:
I adjusted the define as you suggested.
When I use this, I don't use "mount' to mount the image. I run 'atrfs' with the options, and it does the mounting. I turn on debugging, so I typically run:
atrfs -f -s --atrdebug --name=images/testimage.atr ./mnt
That mounts ./images/testimage.atr on ./mnt which I've previously created as an empty directory.
atrfs -f -s --atrdebug --name=a.atr atr1 > log.txt 2>&1
$ ls
DOS XE 1.0.atr atrfs.prev
LiteDOS manual.pdf b.atr
LiteDOS-SE (build 2022-02-07).atr c.atr
TBasic UBasic (No DOS).atr log
a.atr log.txt
atr1 test.sh
atrfs
[eightcore: ~/Downloads/LiteDOS-SE]
$ cd atr1
-bash: cd: atr1: Input/output error
-
I have an older Mac running OS X El Capitan (OSX 10.11.6)
Here is comment in fuse.h
* IMPORTANT: you should define FUSE_USE_VERSION before including this
* header. To use the newest API define it to 26 (recommended for any
* new application), to use the old API define it to 21 (default) 22
* or 25, to use the even older 1.X API define it to 11.
I tried to compile using both 25 and 26, which correspond to the old and new API versions. In both instances, the compilation was successful. However, I did have to modify 'atrfsc.c', changing 30 to 26.
#if (FUSE_USE_VERSION >= 26)
, NULL
#endif
----
I almost succeeded in mounting the atr file to the filesystem:
$ mount
..
..
..
..
atrfs@osxfuse0 on /Users/piotr/Downloads/LiteDOS-SE/atr1 (osxfuse, nodev, nosuid, synchronous, mounted by piotr)
As you can see, I'm using FUSE version 3.10.4 for OSX (FUSE for macOS 3.10.4).
Unfortunately, the mounted directory isn't functioning. I receive an 'Input/Output Error (5)' when I attempt to access it.
Do you have any suggestions on how to resolve this issue?
-
18 hours ago, pcrow said:
Done! I just pushed the change. It has had very minimal testing, so let me know what bugs you find. Remember to always keep a backup of your original files in case my code corrupts your files.
It's fun seeing new DOS versions and noting the design decisions.
Awesome! I will speak with Mr. Atari, and we will conduct tests.
-
13 minutes ago, DrVenkman said:
I tried the files from this ARC file this morning but don't see that the colors are any different in 80 column mode. I still see the typical "aqua" PAL background color instead of the deeper NTSC blue.
This may be user-error, however, or a misunderstanding on my part. I have my VBXE installed in a PAL machine but I would *like* to be able to have the NTSC colors that I am used to.
During the second half of the week, I will test it and report directly to @drac030 if needed.
-
-
Well, actually... I would try the R2514 instead of the R1606G... It seems like it's just the next generation. The same pinout. However, there might be a need for a BIOS/EFI update, and that could be an issue.
At the moment, I don't know where one can simply buy the AMD Ryzen Embedded R2514.
Alternatively, it could be the R2544. Maybe it's worth finding some Micro PC board and transferring the processor from it, as well as possibly the BIOS.
-
Great job! Thank you!
I have a small request, if possible. Could you please add the LiteDOS filesystem? LiteDOS is a compact DOS created by Mr. Atari.
As I recall, it has a filesystem similar to DOS 2.0 but with more space. It's crucial to have both read and write access.
LiteDOS can be used for cross-development for users who have Atari, Fujinet, and a local TNFS server with a mounted ATR image, for example, in the LiteDOS format. Using the CC65 compiler or another, one can perform cross-compilation and then directly run it on real Atari hardware.
It's also important for such software to manipulate the disk, rather than create an entirely new disk that contains files in the directory.
It's important for all types of LiteDOS formats to work - that is, also those with significantly more disk space for data.
Here is the webpage with documentation that includes the filesystem specification:
http://www.mr-atari.com/Mr.Atari/LiteDOS/
At one point, I planned to write such a program in Python so it could run on Win/OSX/Linux, but I ran out of time.
If needed, there's also contact with Mr. Atari, who will surely be willing to help.
-
1
-
-
Congrats! Good job!
Every acquisition of a great service/network/startup/company with capable, valuable people is a step in the right direction. Congratulations to the entire Atari team as well!
-
1
-
-
-
A planned update for the 80-column driver will be tailored to the VBXE core for the NTSC region.
-
2
-
-
A planned update for the 80-column driver will be tailored to the VBXE core for the NTSC region.
-
1
-
1
-
-
1 hour ago, woj said:
Isn't that what Spectre provides too?
A little more advanced.
-
1
-
-
11 minutes ago, wildstar87 said:
Thanks woj! That's good to know. Now I just have to get a Scart cable, and mod it. I'm crossing my fingers that this will finally work out!
@woj,
I can introduce an additional product to the SAVO line that will produce proper synchronization for VBXE without needing SAVO. It will eliminate noise from the Atari and reverse noise from the cable.
-
1
-
-
1 hour ago, electrotrains said:
I did a new version of the PCB last weekend which has the purple pico rotated by 90 degrees with the USB pointed downwards towards the cartridge port. My new boards shipped from China this morning, so I expect to have them in a week or so. Assuming they work fine, I'll post the new version of the PCB & gerber files on github, along with new STL files for the 3d printed shell.
So if you were planning to get PCBs made, you might want to hold off for a week or so.
(For those that haven't read the whole thread, the reason for this redesign is to physically prevent USB connection when the cartridge is plugged into the Atari. That removes the need for any extra components to protect the atari in the event that the device gets power through USB while connected to an unpowered Atari, and keeps it a simple and cheap build.)
Robin
So maybe I have my tiny contribution
It's great that it has been taken into account.
-
2
-
- Input/Output Error 5. So, we need to determine the next steps. Do you have any ideas, or should I try to set up a tunnel and expose the host so you can check it, or should I add debugging in my free time and see what's going on?
It's great that it has been taken into account.
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
ATRFS: Mount ATR files as local directories under Linux or Mac
in Atari 8-Bit Computers
Posted
I've checked 3 images... staring from two standard atrs from LiteDOS dist. archive and 3rd was SDX.. Same results.