Hello
Did you find the drive you were looking for
SONY MP-F52W-00D I have qty 10 of them.
Make me a offer on all 10
Email: Kathy at advantageic.com
Phone: 978-568-0899 ask for Kathy
Hmm... I've sent a number of things to this list which have not ever
shown up here. Curious if I can actually really post to the list...??
I also see that postings from others show up about 5 to 6 days after they
post them. For example, yesterday 11/29, I received gobs of postings
dated 11/24. There will be many days of silence and then all of a sudden
I'll get a bunch of them all at once, that many days behind.
cje
--
Chris Elmquist
mailto:chrise at pobox.com
Does anyone here have pull with Sun Microsystems or know someone who does?
I'm trying to get the right person jazzed up about the idea of a Type 7
keyboard built like a Model M. I've already emailed clickykeyboards.com
about it and they'll do the engineering and design work for about $27k. A
Type 7 sells brand new for around $50. I'm sure people would be more than
willing to pay twice as much for a "Type 7m".
--
David Griffith
dgriffi at cs.csubak.edu
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
On Thu, Dec 4, 2008 at 2:35 AM, Cameron Kaiser <spectre at floodgap.com> wrote:
>> > My laserdisc player harks from 1986, incidentally, and even its SCSI data
>> > interface has no Inquiry support - it was just too early, I suppose...
>>
>> SCSI LASERDISC?!?!?!?!?! I think there were only RS-232 Laserdiscs?!
>>
>> I'd love to have a serial-commanded laserdisc hehehe :o)
I have a few - mostly to play Dragon's Lair and Space Ace (but I do
have a couple of kiosk CAV discs as well). AmigaVision supports a
variety of laser disc command sets, as a classic environment which
could be simple and fun to explore such discs in.
> I recently got an AG-LD30 with a serial interface, but I don't know the
> pinout. It's a 15-pin D female connector, like a PC joystick port or Mac
> monitor port.
I think there's at least one Pioneer with a DA15 serial interface, but
I have no idea if there's any sort of standard for them. If you can't
find a manual for your AG-LD30, there's always the technique of
tracing out the circuit manually. Ground should be easy, then it's a
case of looking for, typically, a 1488/1489 pair and divining what
your RxD and TxD are. It's probable that there's no handshaking, but
I suppose there could be. Not knowing the command set could be a
problem, though. Check out AmigaVision to see if it knows about your
player. You could then sniff the command set with a serial analyzer.
Generally speaking, the player should have commands for start, stop,
and seek, at least, and perhaps lock/unlock, eject, and several more
directives. When writing apps for a friendly environment, start,
stop, and seek are probably the most important commands to figure out.
-ethan
On Thu, Dec 4, 2008 at 3:22 AM, Bob Armstrong <bob at jfcl.com> wrote:
>>PS: while the wrong list, Bob have many people finished the PDP/8 front
> panel PCB's?
>
> I don't know - the majority of people who buy kits never write back to
> tell me what happened.
I must be in the minority ;-) I not only write back, I frequently
post pictures of my successes.
-ethan
________________________________
Hi, all,
I was staring at an SBC I have here with a 6MHz Z-80, some ROM, some RAM,
and a 26-pin off-board bus for some Z80-PIO boards (this thing was built
as a multi-parallel-printer switcher). I've been musing about what it
would take to boot CP/M up on this.
For user I/O, I was planning on a console serial port and a
terminal/terminal
emulator. I have IM6402s on hand, but I'd be interested in hearing if
certain other chips are preferred, based on what BIOS code is floating
around out there. I also have a 16550, but I don't think I have any
Z80-SIO chips handy.
For mass storage, I was planning on either Compact Flash or an SD card.
I think I've seen both as I googled around for modern SBCs. Any of the
media I have lying around is plenty large enough (I even have some 4MB
CFs and a 2.5MB full-sized PCMCIA flash card on hand).
I am a little unclear, though, about how traditional CP/M systems
were set up for ROM and RAM. Was it common to use a "shadow ROM"
in low mem at reset, then have the BIOS live at the top of memory?
How did 64K RAM CP/M machines handle the BIOS? Did they temporarily
ghost the ROM on top of RAM until some bit of code could read ROM
and write RAM then bank out the ROM? Since I think I "need" at
least 48K of RAM, I was planning on a pair of 62256s. I could easily
do 56K of RAM low and 8K of ROM high, I think, unless there's some
other arrangement that's obvious to try for a simple design.
I've never tried writing a BIOS for a CP/M machine, but my understanding
is that things are modular enough that once you know what I/O chips
you have and at what I/O addresses, for a straightforward, non-clever
design, the coding is equally straightforward and non-clever (but please
feel free to enlighten me if otherwise).
Thanks for any tips, especially from anyone on the list who has ever
rolled their own CP/M machine.
-ethan
--
Ethan Dicks, A-333-S Current South Pole Weather at 4-May-2008 at 19:40
Z
South Pole Station
PSC 468 Box 400 Temp -74.2 F (-59.0 C) Windchill -105.4 F (-76.4
C)
APO AP 96598 Wind 7.4 kts Grid 77 Barometer 691.6 mb (10194
ft)
Ethan.Dicks at usap.gov <http://www.classiccmp.org/mailman/listinfo/cctalk>
http://penguincentral.com/penguincentral.html
-----REPLY-----
Hi Ethan,
Funny you should mention the subject, I am working on a very similar
project.
Last year, I made a completely home brew Z80 computer with prototype boards.
It is a fun project and you can definitely build your own CP/M computer from
scratch. It really is not that hard.
This year, I am remaking the design using manufactured PCBs.
I recently got my first batch of prototype PCBs and have been building up
and testing them.
So far, I have gotten the CPU, ROM, RAM, UART, and most of the glue logic
working and tested.
It is not complete yet as I still need to wring out much of the hardware and
have not even started on the PPI or RTC.
However, last year I was able to boot the previous system into its monitor
and even boot CP/M.
CP/M used a 32K ROM drive for drive A:, a 448K RAM drive for drive B:. I
implemented an IDE port and a hard disk for drive C:.
Those all worked pretty good. I built but never tested a floppy drive
interface.
The whole system is pretty simple, uses plain 74LSxxx chips, no programmable
parts (except the EPROM) or hard to get parts.
No SMT or funky technologies, just plain through hole DIP chips.
I have all the software and am presently going through the library
reinstalling it on the new system.
So far, I have most of the easy stuff working. I do have the RAMless
monitor working and next will be the regular monitor.
Finally it will be the CP/M system and the RTC software.
Anyway, if your interested, I am keeping a small Google group of files and
photos at:
http://groups.google.com/group/n8vem
Thanks!
Andrew Lynch
> What is the minimum satisfactory sampling rate if one wanted to emulate an ST-412
> interface and have it RLL (2,7)-capable?
2x, assuming you regenerate the clock. With a digital DLL, the incoming clock would
be on the order of 8x the maximum incoming frequency.
The bitstream is not variable frequency. You can think of what is needed as the inverse
of the read recovery circuit on the drive controller.
The tricky part is generating the recirculating bit stream that you send as read data
back from the simulated drive. It is expecting the data that it just wrote to be in
the data read back on the next revolution. And you need one of these bitstreams for each
head.
> Actually, it's not clear to me if any of the
> bridges supported that command.
I don't know of any MFM/RLL controllers that supported scsi inquire.
ESDI was the first 5" drive interface to support geometry inquiry
which is needed to make inquiry work w/o the host specifying
the drive geometry to the bridge board.
Does anyone have a datasheet for these parts? I have come up empty on
the web and have 24 of them and can't explain why...
Most of the stuff I've had around here used 4116 or 4164 DRAMs and
I kind of suspect these might be a substitute for one of those...
but sure can't remember for sure.
Although, by the part number alone, one might suspect they are a
32Kx1 device possibly...
Any info appreciated.
Chris
--
Chris Elmquist
mailto:chrise at pobox.com