ChanServ changed the topic of ##yamahasynths to: Channel dedicated to questions and discussion of Yamaha FM Synthesizer internals and corresponding REing. Discussion of synthesis methods similar to the Yamaha line of chips, Sound Blasters + clones, PCM chips like RF5C68, and CD theory of operation are also on-topic. Channel logs: https://freenode.irclog.whitequark.org/~h~yamahasynths
Xyz_39808 has quit [Read error: Connection reset by peer]
Xyz_39808 has joined ##yamahasynths
<andlabs>
Foone_: (pointed to you by endrift) what's the best way to get blank 2DD (720k) 3.5" floppy disks nowadays?
<andlabs>
and which type should I go for
Xyz39808 has joined ##yamahasynths
Xyz_39808 has quit [Ping timeout: 240 seconds]
<andlabs>
I probably won't need more than one disk anyway
<andlabs>
though I could keep some more around just inc ase
<andlabs>
maybe we need to start manufacturing new ones
_whitelogger has joined ##yamahasynths
<m4t>
i think you can just cover the hole in a regular 1.44mb and reformat. just like you could convert 720 to 1.44 by punching the hole.
<m4t>
unless you want to be a purist about it
<m4t>
which i would completely understand :P
_whitelogger has joined ##yamahasynths
<andlabs>
I don't know if that would work on the drive of a Panasonic FS-A1F?
<andlabs>
also would that punching a hole trick work on all disks?!
<andlabs>
they're already double-sided...
cr1901_modern has quit [Read error: Connection reset by peer]
cr1901_modern has joined ##yamahasynths
_whitelogger has joined ##yamahasynths
<Foone_>
andlabs: I have tons (I bought like 400 from a former duplicator) so I'd be happy to mail you some
<Foone_>
and converting 1.44mb disks to 720k is not terribly reliable, they have different coercivities
_whitelogger has joined ##yamahasynths
_whitelogger has joined ##yamahasynths
<andlabs>
uhhh sure, if you're down for that option; thanks
<andlabs>
I was just going to ask for advice on what to look for / what to avoid but I guess that works too
<andlabs>
and I suspected DD and HD had different chemical properties
UnluckyPony is now known as SceneCAT
_whitelogger has joined ##yamahasynths
andlabs has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
andlabs has joined ##yamahasynths
Sarayan has quit [Ping timeout: 272 seconds]
Sarayan has joined ##yamahasynths
andlabs has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Sarayan has quit [Ping timeout: 272 seconds]
andlabs has joined ##yamahasynths
<Foone_>
yeh, just message me your address and how many you'd like
<Lord_Nightmare>
400 *BOXES* or 400 loose dsdd disks?
<Lord_Nightmare>
400 boxes you could make an (admittedly small) floppy fort
<Foone_>
it was 2 boxes of 200 each, I believe.
<Foone_>
I partially bought them because DD disks can be rare, and they're really useful for some things that really need them (because they don't work with HD disks) but mostly it was to get an in with the company. They are from CopyPro, who are local, and built some of the floppy disk duplicators I own
<Foone_>
so I was trying to get them to look through their storage and see if they can get me some extended hoppers and such
<Foone_>
I did manage to get them to do that, but sadly they didn't have any left over. so I never got them
<Foone_>
that's why I ended up doing the 3D printed + lasercut hopper I have now
<cr1901_modern>
hopper?
<Foone_>
it's the part you load all the blank floppies into, and it mechanically inserts them one at a time
<Foone_>
(I have like 90 threads on this project, because I was working on it for the second half of 2019)
<Foone_>
are they linked together in any way or posted on my wiki? (which is supposedly for doing exactly that) NOPE!
<Foone_>
so good luck finding info on it. I really need to work on it a lot.
<cr1901_modern>
Basically, I'm wondering: Do I need a hopper?
<cr1901_modern>
I don't write floppies that much anymore, but it seems convenient for writing them out
<Foone_>
depends how many floppies you have to duplicate! the standard hopper fits like 30 disks so you can just keep it topped up
<Foone_>
I only built the extended hopper because I'm retrofitting this duplicator into being a disk imager
<Foone_>
so it'll be able to automatically image disks and I want to be able to load LOTS to do that.
<cr1901_modern>
How does it work? I see a chute for holding floppy disks that does into a metallic part at the bottom
<cr1901_modern>
and then a green chute that presumably ejects the disc?
<Foone_>
the metallic part is the main disk copier mechanism. it has a motor that inserts disks from the hopper, and then can eject them when done. the green thing is the "slide", and it has a servo which stops the disk from going all the way down
<Foone_>
then while it's stopped, a picture is taken, then the servo lets it drop the rest of the way
<cr1901_modern>
Oh, did you design the mechanism that loads the disk into the drive?
<cr1901_modern>
Also, how does that servo on the end prevent the disk from sliding off? :P
<Foone_>
no, the metal part is all stock from the CopyPro 2000 disk duplicator. I'm using it as-is, I've only replaced the control PCB with my own microcontroller-based system
<Foone_>
in any case, the project is currently on hold for a couple reasons: 1. I need to figure out how to improve and simply the photographing system 2. I need to reprint the slide. I tried to move it aside and accidentally broke it, right when my 3D printer broke
<Foone_>
I've gotten a new 3d printer now but I'm still in the "settling in" phase so I'm not ready to jump back into reprinting the broken parts
<cr1901_modern>
From what I've seen, I'm better off getting someone else to 3d print for me rather than getting my own
<cr1901_modern>
b/c good ones are too expensive, and cheap ones are, well, bad
<Foone_>
probably. 3d printers are currently more of a hobby that a practical machine you get and just use
<cr1901_modern>
hrm :/
<Foone_>
you spend about as much time upgrading and repairing it as you do actually using it for things
<cr1901_modern>
That's not fun. I have some parts I'd like to print to repair some old PC equipment (go figure), but haven't been arsed to make them
<cr1901_modern>
I don't need to spend extra time fighting with the printer
<Foone_>
have you seen that TCRF thing about how old EEPROM burners worked that way too? they'd malloc a buffer and then compile into that, then burn the whole buffer
<Foone_>
so if you have a 40k game on a 64k chip, you'd get 24k of random shit that was in RAM beforehand
<cr1901_modern>
Yes, this is the reason the Sonic 2 Nick Arcade proto has some of it's own assembly code in it
<Foone_>
and the mask roms get created by sending (E)EPROMs into the mask-rom manufacturer, so naturally the data is there, too
<cr1901_modern>
either because the assembler stored artifacts onto the disk image, or the EPROM burning process stored artifacts from memory
<Foone_>
there's some gameboy prototype that has bits of their netscape cache in it, so we know which porn site they were looking at before hitting compile
<cr1901_modern>
... okay, which proto is this?
<cr1901_modern>
For research purposes
<Foone_>
one sec, lemme find it
<ej5>
iirc the Amiga kickstart 1.0 disk (256k of boot "rom") contains a bunch of random files in the remainder of the disk, including source code.