I'm trying to negotiate the sale of some rare E&S graphics gear, but
the person is located in Battle Creek, MI and isn't willing to ship
the item.
Can someone help me out with transporting the item to the Craters &
Freighters office in Detroit? I can paypal you money for your gas and
time.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>
Looking at the image on the linked page, I'm wondering what kind of a dual
drive setup that is. Mine doesn't look like that.
---------- Forwarded Message ----------
Subject: [FG] WarGames: A Look Back at the Film That Turned Geeks and Phreaks
Into Stars
Date: Thursday 24 July 2008 00:39
From: "Steve Gunhouse" <svgunhouse at woh.rr.com>
To: "fidoguns at fidoguns.org" <fidoguns at fidoguns.org>
<http://www.wired.com/entertainment/hollywood/magazine/16-08/ff_wargames>
Was it really 25 years ago?
--
Steve Gunhouse
-------------------------------------------------------
--
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space, ?a critter that can
be killed but can't be tamed. ?--Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James
M Dakin
Looking for some advice on the ET-1000. I think Heath trainers were
discussed here not too long ago. I have an opportunity to buy one
locally for what I think is a fair price. While it would be nice to
own as a relic, I'd like to actually use it as well (I intend to begin
an electronics curriculum in the Fall.) It seems to have the features
I'd need, and I'm assured it's working properly, but is too vintage to
use regularly? Would I be better off just going with some Rat Shack
kit?
Thanks to all
--
j
The 765 does the skip of index gap thing regardless of VCO connection
an that is triggeerd off the index pulse.
VCO inhibit is there to prevent the PLL from trying to track the the mistiming
an index gap can introduce. Not always required and some VCO designs are
better behaved.
Allison
>
>Subject: Re: Floppy controller Q - VCO Inhibit / VCO Sync, and IBM format
> From: "Chuck Guzis" <cclist at sydex.com>
> Date: Tue, 29 Jul 2008 14:49:23 -0700
> To: "General Discussion: On-Topic and Off-Topic Posts" <cctalk at classiccmp.org>
>
>On 29 Jul 2008 at 20:55, Philip Pemberton wrote:
>
>> At the moment it's driven permanently high; this seems to work OK insofar
>> as the sync detector (which is why the datasep is there -- to extract a clock
>> signal for the MFM data stream) will pick up SYNC-A1 signals and the data
>> seems to be valid. What I don't know is if this is how things are supposed to
>> be done...
>
>ISTR (and it's been a long time since I read the document) that the
>later versions of the 765 (765A?) imposes something like a 500 usec.
>VCO inhibit after the leading edge of INDEX/. Earlier versions (765,
>8272) imposed something like a 1000 usec. VCO inhibit. This can be a
>real problem if the original disk was not formatted with an IAM,
>leading to failure to recognize the IDAM for the first sector on the
>track.
>
>Even so, the 500 usec. "blind spot" exhibited by the 8272A/765A can
>be a problem for diskettes formatted on other systems where a too-
>short gap occurs before the first sector header. This leads to all
>sorts of dodges in reading them on PCs, such as taping over the index
>hole or tweaking the drive spindle speed down a bit.
>
>WD controllers of the 17xx family did not do this; you could start a
>sector very close to the index pulse and still be fine.
>
>My advice would be to fuggedaboudit, particularly if you want to read
>diskettes produced on other systems than PCs.
>
>Cheers,
>Chuck
>
>
>
>
>
>>
>> The uPD765 and 827x datasheets are predictably rather sketchy on this
>> front... All they really say is that the VCO line inhibits the VCO in the PLL,
>> which would have the effect of allowing the PLL's loop filter to discharge,
>> and reset it to a predetermined state. What they don't say is under what
>> conditions the FDC will do that...
>>
>> So I guess the million dollar question is what I should do with said VCO line.
>> Wire it to /INDEX via an inverter to reset the PLL on every rotation? Or just
>> wire it to VCC (VCO enabled) and leave it?
>>
>> Thanks,
>> --
>> Phil.
>> classiccmp at philpem.me.uk
>> http://www.philpem.me.uk/
>>
>
Hi all,
What's the current status as to the copyright and reverse-engineering of
Teledisk's archive format? I have a feeling that someone was working on
documenting the file format, but that the copyright is still owned by some
company or other (not Sydex any more)?
cheers
Jules
>
>Subject: Floppy controller Q - VCO Inhibit / VCO Sync, and IBM format
> From: Philip Pemberton <classiccmp at philpem.me.uk>
> Date: Tue, 29 Jul 2008 20:55:04 +0100
> To: General Discussion: On-Topic and Off-Topic Posts <cctalk at classiccmp.org>
>
>Hi,
> I've been playing about with the HDL code for the floppy reader (after a
>"short break") and started thinking about how the VCO Sync/Inhibit line on the
>data separator should be driven.
>
> At the moment it's driven permanently high; this seems to work OK insofar
>as the sync detector (which is why the datasep is there -- to extract a clock
>signal for the MFM data stream) will pick up SYNC-A1 signals and the data
>seems to be valid. What I don't know is if this is how things are supposed to
>be done...
>
> The uPD765 and 827x datasheets are predictably rather sketchy on this
>front... All they really say is that the VCO line inhibits the VCO in the PLL,
>which would have the effect of allowing the PLL's loop filter to discharge,
>and reset it to a predetermined state. What they don't say is under what
>conditions the FDC will do that...
The VCO is allowed to hold at nominal freq during index gap. It's in the
datasheet and a time after index.
The VCO filter should not discharge but insead remain at niminal frequency
rather than seeking phase lock. This is PLL 101.
>
>So I guess the million dollar question is what I should do with said VCO line.
>Wire it to /INDEX via an inverter to reset the PLL on every rotation? Or just
>wire it to VCC (VCO enabled) and leave it?
The VCO line is an output from the FDC to the PLL. Some systems do not use it
other use it as specified.
Allison
>Thanks,
>--
>Phil.
>classiccmp at philpem.me.uk
>http://www.philpem.me.uk/
Hi All,
I've run into a problem with TCP/IP on AIX 3.2, hopefully someone can
shed some light on this weird problem. I've used smit to configure the
network - which works fine within the subnet. The gateway points at the
building router (x.x.132.1), and, a netstat -rn returns this on the
default route as well.
But, no traffic gets out of the building. A traceroute shows the first
hop is made to x.x.132.63, where it dies - a seemingly random PC, which
is not in any configuration file on the system. Any ideas why this
might happen?
T.H.x.
Devon
Hi,
I've been playing about with the HDL code for the floppy reader (after a
"short break") and started thinking about how the VCO Sync/Inhibit line on the
data separator should be driven.
At the moment it's driven permanently high; this seems to work OK insofar
as the sync detector (which is why the datasep is there -- to extract a clock
signal for the MFM data stream) will pick up SYNC-A1 signals and the data
seems to be valid. What I don't know is if this is how things are supposed to
be done...
The uPD765 and 827x datasheets are predictably rather sketchy on this
front... All they really say is that the VCO line inhibits the VCO in the PLL,
which would have the effect of allowing the PLL's loop filter to discharge,
and reset it to a predetermined state. What they don't say is under what
conditions the FDC will do that...
So I guess the million dollar question is what I should do with said VCO line.
Wire it to /INDEX via an inverter to reset the PLL on every rotation? Or just
wire it to VCC (VCO enabled) and leave it?
Thanks,
--
Phil.
classiccmp at philpem.me.uk
http://www.philpem.me.uk/
Definitely the right netmask, and seems to be the right interface (en0) -
although, as a side note, can you explain the difference between this and
the et0 interface? No problems with any other system in the
building. I've set up many a solaris or linux box with no problems.
arp -a shows nothing interesting, just another system I ftp'd into - have
tried adding a static entry for the gateway, with no luck:
? (xxx.xx.132.118) at 0:b0:d0:26:7b:5d [ethernet]
the netstat -rn (x's added, obviously):
Routing tables
Destination Gateway Flags Refcnt Use Interface
Netmasks:
(root node)
(0)0 ff00 0
(0)0 ffff ff00 0
(root node)
Route Tree for Protocol Family 2:
(root node)
default xxx.xx.132.1 UG 0 472 en0
127 127.0.0.1 U 50 340667 lo0
xxx.xx.132 xxx.xx.132.191 U 11 1773 en0
(root node)
Route Tree for Protocol Family 6:
(root node)
(root node)
T.H.x.
Devon