Jump to content

E474

Members
  • Content Count

    629
  • Joined

  • Last visited

Community Reputation

271 Excellent

About E474

  • Rank
    Dragonstomper

Contact / Social Media

Profile Information

  • Location
    Coimbra, Portugal

Recent Profile Visitors

3,281 profile views
  1. My version that I had to resume the download of extracted fine with 7z (on Linux) and a test unzip of Zork I - The Great Underground Empire Rel 20 (1981)(Infocom)(US)[disk].zip worked fine with atari800 4.1.0 though I got an error/info message (which didn't cause any problems): Unknown VAPI track type Track:1 Type:256 @HatNJ, what platform/OS/etc. were you trying with, and did you get any error messages, etc?
  2. Hi @Timothy Kline, Thanks for hosting, thought I should give you a heads up on the problem (and possible workaround, e.g. using a file downloader that supports resume). I used either NextCloud or OpenCloud on a RPi for a while and it worked quite well until they upped the requirements for the type of Pi you could use (if I recall correctly).
  3. I got nothing trying to download the torrent and gave up after 3 hours. The file download provided by @Timothy Kline closed the connection every 500MB (exactly, so probably a setting in ownCloud), but I used uGet, which allows autoresume. The error listed was: Message: HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)
  4. Isn't it supposed to include a tracker URL? I opened the torrent file using http://torrenteditor.com/ - and it was missing. Not created a torrent file myself, but I thought this was required? I went from https://lifehacker.com/how-to-share-your-own-files-using-bittorrent-5534190 - so I might have got this wrong though.
  5. Hi, Is it possible to have a virtual keyboard on the atari800 emulator on the GamePad, running under RetroArch (on a softmodded WiiU). I saw a comment on a WiiU video on YouTube (ages ago) that this was possible, but didn't follow up with the question of how to do this. I assume it's a configuration file setting, if it's even possible, as there is nothing in atari800's UI to do this. I'm running atari800 3.1.0 (b59fb7e), which is the latest version in the WiiU RetroArch (AFAIK). I think I can plug in a USB keyboard to the WiiU, but having a virtual keyboard, as used by most tablets, would be a bit easier. Anyone know anything further? TIA!
  6. Hi @cbelcher, Are you going to share the PCB/Kicad/source files too (I appreciate it's a simple circuit)?
  7. HI @_The Doctor__ (am reacting to your "confused" emoji), The FujiNet config program cc65 sources are on GitHub (link supplied), so the Makefile and linker configuration info (and any other requirements) are available, and would, most likely, just need copying and pasting (and maybe renaming) to be used by @Fabrizio Caruso in their Cross-Lib project. Hope this helps (assuming this was the source of confusion)!
  8. Have a look at the FujiNet config program (coded in cc65), the makefile generates an atr: https://github.com/FujiNetWIFI/fujinet-config To build: run make clean && make dist this will clean the build tree, and make a new disk image called autorun.atr which can be copied to the data/ directory in fujinet-platformio for firmware updating.
  9. Ah, OK, wouldn't a settings buffer solve this, just update any changed values, and write out the whole buffer on save (I assume this isn't done with the current code, though)?
  10. Hi @reifsnyderb, I got Visual Studio up and running on Debian Bullseye (64 bit), I just did (in a shell script): #!/bin/bash sudo apt-get update sudo apt-get upgrade sudo apt-get install build-essential git python3-venv python3-distutils wget apt-transport-https cc65 wget -qO- https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor > packages.microsoft.gpg sudo install -o root -g root -m 644 packages.microsoft.gpg /etc/apt/trusted.gpg.d/ sudo sh -c 'echo "deb [arch=amd64,arm64,armhf signed-by=/etc/apt/trusted.gpg.d/packages.microsoft.gpg] https://packages.microsoft.com/repos/code stable main" > /etc/apt/sources.list.d/vscode.list' rm -f packages.microsoft.gpg sudo apt update sudo apt install code sudo usermod -aG dialout ${USER} Though that also includes installing cc65. I cribbed adding the Visual Studio Code repositories from: https://code.visualstudio.com/docs/setup/linux - which also includes steps for other Linux distributions. This came up in a FujiNet thread:
  11. The 8-bit specific drive circuitry would be an interesting project to reproduce, given there must be a lot more 360K PC drives than 1050s (I guess).
  12. There are some on AliExpress, they look like pull out compartments/draws that fit in a PC case.
  13. It looks like a standard 5.25" PC drive up until the air vents, with (I would guess) the 8-bit specific hardware in the rear 3rd of the case. Nice find!
  14. Hi @hatchcliff, Thanks very much for updating us all on this, I don't know enough about packaging to offer a lot of advice, but I think I would go with option C as it is putting the decision into the hands of the end user. I saw @HiassofT mentioned there was a split on RPi 0/1 using the old graphics architecture/driver, and there is also the Pi4 versus Pi3/2 architecture (64 v 32 bit), so maybe there are 3 packages to be built? Also, the Pi1 can be over-clocked, so it might be possible to get atari800 up and running, especially given the notes from Hias on the old versus new graphics driver, and being a bit brutal with removing installed packages, Window Manager and Desktop Environment, etc. (I guess?). I also think using the update-alternatives mechanism might simplify things, as it gives the opportunity to explain the context for the choices, using a uniform front end. Perhaps checking in the program if the package is actually correct for the RPi it's being run on, and issuing a (skipable) warning if it isn't, is the simplest approach, at least that way the user is notified if they have installed the wrong package, or if the package is running on hardware that has just been released, and is yet to be fully tested/supported. It also provides an opportunity for the user to install the package of their choice for people who have an unusual configuration, etc. I don't understand why there are 2 different configuration files, isn't it better to just ignore configuration options that don't apply? Also, sorry to hear you aren't enjoying the packaging process, I wasn't very happy about not having an atari800 executable on the Pi, but it's not so good when people don't enjoy the situation to the point where they no longer want to get involved. I remember the RespeQt developer also stopped work on that project as it stopped being fun, I'm sure other people have also stopped for similar reasons, and I think we are all the poorer for that.
  15. A Lazer drive will definitely read US Doubler disks, both support Double Density (256 byte sectors, 720 sectors per disk). The Lazer board is a hacked Happy board, there is an ATR I posted with utilities specific to the Lazer in another thread, which should show up in a forum search. You should be able to figure out which way round the board goes by figuring out which pins on the 6502 are +5V and Ground, then seeing where the traces go to the pins that go to the board connector, and matching them against the pin outs for the 6507, which is the socket that the board will go into. It's a bit tedious, but I can't think of a reliable way otherwise. Just try Googling for the 6502 and 6507 datasheets (unless anyone knows a simpler method)?
×
×
  • Create New...