Jump to content

wierd_w

Members
  • Content Count

    1,621
  • Joined

  • Last visited

Everything posted by wierd_w

  1. OK. I will pull the tarball, and set it up with that. Is the tarball sourcecode? EDIT: Tarball is 64bit. Will not run in i386!
  2. VM now automagically starts X when normal user logs in. This automagically starts MAME. When mame exits, "sudo poweroff" is called, causing a graceful shutdown. Appropriate rules to not demand sudo password for poweroff command has been added to /etc/sudoers (Normal user is named "genevian", and it is a member of sudo group.) Still need to do: Kill GRUB screen/timeout Autologin as "genevian" Make MAME automagically start geneve emulation
  3. I was meaning, that is the newest that is in the debian repo for i386 If you can give me a ppa that keeps it current, that would be great. I would add it.
  4. OK, I have the virtual machine able to start mame with a minimal xwindows and twm. I suspect it is an ancient version of mame, however. Is there a repo I can add? TODO: Figure out how to make MAME auto-start Geneve emulation Remove GRUB2 bootloader timeout Autologin, and automagically run startx. Automagically invoke "sudo shutdown --now" when mame exits. (DONE! VM now downs gracefully when you kill MAME)
  5. OK. I will do the following: step 1, create a flat image VMDK in virtualbox that is 1gb 2gb in size. (Base debian is bigger than I expected) step 2, install debian using netinstall cd, with hyper minimal options. Step 3, configure the VM as I desire. Step 4, use DD to transfer this image (with /etc/fstab entry calling for GUID of filesystem for root volume) to a USB stick. Step 5, verify operation then, when all works as expected: Step 6, zip the resulting image and post it. Since this is probably going to be aimed at "old hardware", I will use the i386 branch debian, not x64 branch debian.
  6. hmm.. I suppose I could dig out that modded chromebook, and do a proof of concept with it?
  7. If I were to try and make it as light as possible, I would: 1) Start with a fresh debootstrap (or similar, such as say, arch base) environment; Just enough to get a console, and functioning network stack. 2) Install X and fluxbox (to get a functional skeleton xwindows config we can modify) 3) Modify the X config for fluxbox, and substitute mame's executable instead. This way there would a hyper-minimal init, hyper minimal x, and just the bare necessities. Specifically, after this is done, you will have functional xinit configuration you can prod. https://wiki.archlinux.org/index.php/Xinit#xinitrc We would edit it, and prevent it from starting fluxbox. We would instead direct it to start mame, and append the ampersand at the end, as instructed.
  8. Does the hardware have to be used on the 99? I really would like a newer 3D printer with a bigger, self-leveling bed, and twin nozzles. (that way I could use PVA filament for supports and the like.)
  9. Microsoft's BASIC was actually a lot of places. Like here: https://en.wikipedia.org/wiki/Atari_Microsoft_BASIC Wikipedia has a pretty good list of places in its main page for MS Basic. https://en.wikipedia.org/wiki/Microsoft_BASIC EG, it was more than just QBASIC and pals.
  10. (somewhat confused that nearly all the BASICs mentioned live on 8bit micros, with very little love for any of the BASICs on PC. No mention of IBM rom basic? No mention of MS's BASICs?)
  11. I had a radical idea, and did a quick proof of concept test, for diy projects that simply must have conductive membrane. I just took a small square of foil emergency blanket and applied concentrated muriatic acid to it with a cotton swab. I was successfully able to remove the foil backing from the blanket where it was treated. (You need to test which side is exposed foil) The resulting salt in the cotton swab is grey, which is consistent with aluminium foil coating. It should be possible to do chemical film deposition of copper onto that with dilute silver nitrate and copper sulfate solutions (to make solder pads that stick). Painted resist could be used to mark areas to retain metalicity for full acid wash. I wholly recommend a proper pcb for keyboards though. I only mention this as a technical aside for tinkerers to play with.
  12. There *ARE* soft/rubber-like 3d print filaments. They are hard to work with. See this TPE (Thermoplastic Elastomer) filament. https://www.amazon.com/eSUN-Elastic-Flexible-Printer-Filament/dp/B01A4WP4AY I would think a better solution would be to print a wholly-new backplane to completely replace the mitsumi keyboard. It should be possible to print channels for wires to be easily tucked into, on a rigid flat sheet of printed plastic that has holes for discrete switches to be mounted on. Then you just wire-wrap, solder, and tuck. Still.. It MIGHT be possible to print a replacement sheet, it just probably would be far more trouble than it is worth.
  13. I am not so protective of my items. Probably should be, but am not. If I needed a dust cover, I would make my own though. (In addition to making lovely baked goods, I can also crochet, knit, and sew.)
  14. To be perfectly fair, I saw the bulging candy eyeballs at walmart, and the image of "Terrified" gingerbread men gave me great delight. Shame that my cookie cutter does not give them a very big head-- I would have loved to put frightened mouths on them with the pastry bag too.
  15. Merry christmas. I made some cookies for my old people.
  16. The cyrix also had a NASTY reputation of having a rinky-dink sized on-die cache size, in addition to its poor integer math performance. This translated to quite a few performance issues when running win9x, which made excessive use of context switching, and thus would suffer issues from cache exhaustion. Since systems that had cyrix cpus often had little or no external cache to speak of, the problem was greatly compounded. (See also, Packard Bell with Cyrix CPU.) This is not to say that a system with a cyrix cpu was guaranteed to be a potato; Just that the circumstances leading to the use of a cyrix CPU, often resulted in a slew of additional contributory factors, ultimately resulting in peak potato-ness 9/10 times.
  17. Up until middle/highschool, my school system used Apple II/e and 68k & early PPC Macs. (everything from cheap LCs to G2s) They later switched to PCs, and all the teachers suffered serious "mac user syndrome" trying to adapt to it.
  18. I have/had taken some time away from it, so that I could focus a little energy on my residents at work, (Been doing a lot of baking and stuff there, and cooking up some turkey to share with my co-workers, due to the whole covid thing-- We have to be in each others' company anyway to do our work, so my thought was that it was a good idea to do in that limited scope.) Also, it's Computer Based Training time again... which means mind-numbingly stupid and repetative videos ad-nauseum. I will certainly get back to it as soon as I have recharged a bit.
  19. I rather like my expensive CATIA seat. Mainly because I know how to use it very well, but also because it has a very nice built-in sterolithography function for making very nice .stl files.
  20. I recently did some plumbing repair, and was "very pleased" by how well PVC adhesive sticks pipe together. For a solvent weld, it does an amazing job. So, I wondered if you could PVC filament. Turns out, YOU CAN. I am seriously contemplating ordering some of the black, then doing some tests with PVC pipe glue. It could make for interesting builds that are not easy to accomplish otherwise.
  21. It has probably already been said, but the Apple II was created in the same vein as the Apple 1: As close to "A real computer" (eg, a domestic version of a mainframe with a single seat) as one could get, on a home-owner's budget. To attain that, a hyper-optimized architecture was created that got the very most bang possible, for as little buck spent. To make it look swanky, Jobs gave it an iconic exterior; but all the things that make an apple II an apple II, came from Woz-- everything from the novel design of the floppy controller to the shared video and system memory. Cost savings while retaining as much high performance and reliability as possible, was the over-arching design philosophy. It was meant to be a real computer, at a bargain price. That's what it was.
  22. it might be possible to print "retainer clips". Since the legs would be vertical, it might be doable. Then it could be monolithic.
  23. I was a child in the 80s. Surely you folks remember the "GUN PANIC!" that happened in the late 80s to early 90s, where every toy gun had to be "Obviously Not A Gun!" in appearance, by law?
  24. Is there a maximum size restriction on the printing service for these .stl files? It might be possible to do one that does not need to be split, with some rethinking of the PCB retention.
  25. Use an older burning software, and do it as a Disc-at-once burn session. Burn it at the slowest speed the disc media supports. Be sure that ISO9660 is used, with Joliet extensions (aka, High Sierra)
×
×
  • Create New...