Search results

there is definitely going to be more latency induced using usb midi interfaces compared to serial based interfaces due to the fact that usb introduced and required a large driver stack (for the time) where as the older printer and serial ports were running as pretty low level direct access...

yup the pre-made cable should be pretty easy to terminate into a IDC 10 pin female header socket without much trouble in regards to the two IC's the larger 16 pin one is a Geoport/localport line driver, so basically a RS422 dual line driver...

mini din 8 pin panel mount sockets are still made and sold along with pre made pass though adaptors too. then you'd jsut need to drill a hoe for the din socket and the two mounting screw onto a standard pci slot cover not sure where your located or what you skill set is but it wouldnt be hard...

they might cost more buy solid polymer caps are generally what i use on everything these days that gets recapped. considering they are the same footprints as electrolytic and don't have the same potential long term issues of leaking or drying out for me it makes sense. to be fair modern...

i swear i read somewhere years ago that the airport slot swapped a few pins around to prevent normal PCMCIA cards working, but the airport cards would still in fact work in a PC laptops PCMCIA slot, in the 2010's i tried out a few different card in my eMac and some got detected and some didnt...

@François its likely that without a monitor connected to the normal db15 video out that mac detects all three sense lines as unconnected/floating so it makes the assumption no display is connected and doesn't enable the video out circuitry on the motherboard. if you have a mac db15 to VGA...

@noglin i think mostly the mirror cable probably just ignores sense ID bits and goes on whatever sense id is configured on the internal harness. at least that would make logical sense to me. connecting sense ID 0 to ground was just a easy way to test a widely supported res and refresh rate as at...

i just had a read up on you thread on the build progress. you mention over there that about removing the hdmi port. it shouldnt be to hard to do if you can remove the solder from the four pins going through the pcb then either hot air or drag soldering the iron on the hdmi pins topside should...

to compile Sheepshaver on raspberry pi see this thread about halfway down: https://www.emaculation.com/forum/viewtopic.php?t=11017 also see this guide for getting Qemu m68k and PPC running on a raspberry pi: https://biosrhythm.com/?p=2837 hopefully there's a bit of useful info there to point...

you might find running mac os 7.5.5 or 8.1 using Qemu m68k (or even perhaps basiliskII) a better fit for a Pi4. 68k emulation runs pretty good on the Pi hardware. ive never really considered running PPC emulation viable on these ARM boards due to the single core performance. thought apparently...

@noglin i dont think the brightness and contrast controls would be needed as they are just so you can adjust those from the front panel buttons or in software depending on the machine.. id be interested what happens it you disconnect those two connections though from what you said each...

@noglin i would expect that your video out issues are due to the fact that these machines need the monitor ID pins set so they display the correct resolution/frequency. S19, S20, S20, S21 need to get wired up correctly to get the right signal. if you ground Sense 0 (Monitor ID 0, S20)to Ground...

no worries, It’s a later version of the SSCI/link driver that I made a standalone installer for. I wasn’t sure if it would work on non English system installs. I’m not sure why you had issues with large ftp transfers though. Regardless performance with a LC PDS card is going to much better...

try this and let me know if you have any success

@mogs i dont think it would be to crazy firmware wise.. ive been pretty busy with life lately so i havent had much free time and to be fair im much better with hardware the writting C code. however i think the ZuluSCSI code already has alot of whats needed already there. the main thing at least...

not sure if ive messed up my testing but for me on SE/30 running vanilla 7.5.5 i get 160KB/s with MacTCP v2.1 with Open Transport (v1.1 according to get Info) i get 64KB/s after installing OT v1.3.1 i get 64KB/s worth pointing out that i use SpeedCopy extension so i haven no idea if that skews...

from what i read it does allow hotplugging of a sd card. however in the case of a mac that would still require a bus rescan and will still pick the scsi id of whatever hdd images are on the sd card. whats needed is for the firmware itself to report to the host (a mac in this case) as a fixed...

what works for me: if the caps had leaked at all i find that using a fiber brush pen on the solder joints before i apply fresh solder helps alot then i add fresh/extra solder before i either use some desolder brainf or my desolder gun sometimes for through hole parts it helps to used s hot...

its something thats crossed my mind a lot over the last couple years (ive probably even mentioned it at times here too). to make a modern zip or jaz style sd scsi drive solution. basically a sd card scsi solution that has a fixed scsi id or better yet a set of jumpers like old scsi drives did to...

thanks, i was able to get afppasswd working now. in fact the instructions you just gave make much more sense then the manual page ive used netatalk on an off over the years since either v2.0 or 2.1 and i definitely agree that the config files used to be full of bloat. i used to just delete them...