> -----Original Message-----
> From: Chris [mailto:mythtech@Mac.com]
> Humm... but this still won't work for PSX game discs right?
> Since they
> have a bad checksum, a standard burner can't write them back
> out, because
> it will correct the checksum?
Well, you've answered your own question there. My understanding is that it
_is_ the burner that does it. You can copy playstation game discs fine, but
it would require a firmware patch to your CD burner. (So I hear...)
Regards,
Chris
Christopher Smith, Perl Developer
Amdocs - Champaign, IL
/usr/bin/perl -e '
print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");
'
I should add to the list of hard to find stuff early Intergraph
workstations. Clipper based, and pre-clipper (were they VAX?) Intergraph
systems.
I also haven't looked -- but have never seen any DG Nova stuff around. It
may be relatively rare.
On another note, CDC hardware that wasn't OEM'd from SGI seems relatively
uncommon. There's one CDC workstation that was a re-badged Indigo, that's
relatively common. It's the only CDC system I've seen for sale.
Regards,
Chris
Christopher Smith, Perl Developer
Amdocs - Champaign, IL
/usr/bin/perl -e '
print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");
'
From: Ben Franchuk <bfranchuk(a)jetnet.ab.ca>
>
>Having looked at a few other Floppy disk datasheets for the pc, I would
>suspect
>it needs a 24 Mhz clock. I can divide this by 2 to give me 12 Mhz clock
>for the
Either some product of 9.6mhz (for the oddball 1.2mb 5.25 floppies) or some
product of 16mhz for the 500khz 1.44mb floppy. That is of course for the
floppy side interface only. The CPU side is driven by Tacc for the FDC IO
ports (4 or 8mhz depending on part and age) and the data rate for read
or write since there is no silo on the parts I know of. This will be true
for all
765 based FDCs (most of the PC controllers are 765 or 765 core logic).
Data rates for 1.44mb floppy are the worst at 13uS first byte and 16uS
for the remaining.
If DMA is possible do it. If not can the cpu execute a wait state during
IO{wait
on data ready with the read or write pending}? If neither of those then you
have
to loop and test status or worse usually, use interrupts.
It's possible to find WD FDC drivers around but they will be very machine
specific more often than not.
Allison
Hand made, usually by women working under low
power microscopes.
Allison
-----Original Message-----
From: Ron Hudson <rhudson(a)cnonline.net>
To: classiccmp(a)classiccmp.org <classiccmp(a)classiccmp.org>
Date: Sunday, December 16, 2001 6:01 PM
Subject: was "how to clean".. How did they
>or... silly question of the week...
>
>
>Anyone know how core memory was made?
>
>Did a person string those cores with a needle and
>"thread", or was it done by machine?
>
>
>I based my statement upon information gleaned from conversations with my
>customers, 80% of which are black. Most of them think that Kwanzaa was
>"made up" by retailers in order to get their money. Some have told me that
>they resent the "social engineering" aspect of Kwanzaa. Here in the South,
>there seems to be very little support of or identification with this event
>among African-Americans.
Oh, you need to come up here, and visit the heavily black neighborhoods
of Jersey City (conviently, right where my wife grew up)... there,
Kwanzaa is a big deal, and it has NOTHING to do with retailers getting
their money. It has everything to do with their not celebrating christmas
because that is whitey's holiday, and crackers are the enemy (their
terms, not mine... I get "whitey"... I get "white bread"... but
cracker?!? I would ask when visiting my inlaws... but I would just get my
ass kicked, or worse, shot).
As to the REAL reason for Kwanzaa, I have no idea, but I do know, around
here it is entirely a racial thing, and the only people that really seem
to take it seriously are the inner city high crime area
Afican-Americans... which unfortuantly gives the whole thing a bad notion
up here. Its a shame really, as I am sure there was a real reason for it,
but like many other things, it has been badly perverted by a very very
select group of people who decided to use it for their own agenda.
-chris
<http://www.mythtech.net>
> From: Sellam Ismail <foo(a)siconic.com>
> Programmers were, are, and will
> always be lazy and impatient.
Man alive -- I always knew I was stupid for putting in all those 80-hour
weeks, but lazy? And impatient???
Glen
0/0
! >Same experience here. i've made copies of IRIX CDs, and I've made
! >non-standard bootable distribution CDs. The only unusual
! >feature is that
! >they're an EFS filesystem rather than, say, ISO9660. But as far as a
! >burner is concerned, an image is an image, and as far as
! >Linux's dd command
! >is concerned, the same is true (I've copied Apple CDs the
! >same way, by
! >dd'ing from the raw disk device holding the CD, to a file.).
!
! Humm... but this still won't work for PSX game discs right?
! Since they
! have a bad checksum, a standard burner can't write them back
! out, because
! it will correct the checksum?
!
! What I don't understand is, why can't someone write a program
! that will
! write the back check? I used to have a floppy disk copier for the Mac
! that did something similar. If the source disk was damaged, it would
! write the damaged data to the destination disk (the software
! was SUPPOSED
! to do that, it was to let you duplicate bad disks before
! running things
! like MacTools on it, in case it didn't work, you could dupe
! it again, and
! try something different)
!
! Alas, that software was for back in the "Classic Mac" era,
! and no longer
! runs (nor has any idea how to write to a CD)
!
! -c
!
I heard that CloneCD is what you're talking about...
--- David A Woyciesjes
--- C & IS Support Specialist
--- Yale University Press
--- mailto:david.woyciesjes@yale.edu
--- (203) 432-0953
--- ICQ # - 905818
From: Richard Erlacher <edick(a)idcomm.com>
>> Munged
>> wacky formats like using deleted address mark for address mark {you can
post
>> format with deleted data} and it was not designed to pump out all the raw
>> bits/splices/marks from the media.
>>
>What? I do seem to remember that the data fields could be written during
>formatting with the WD parts but I don't think anybody ever used that
feature,
>though it would have been a good/smart feature for software duplication.
There
>was some confusion about whether it worked properly because the part
responded
>to some bytes by generating an address mark, though I doubt it did that
while
>writing the data field.
Two differing things. The WD part you could format a disk with Deleted data
marks
where data marks are normally found. Infact you could put all sorts of odd
stuff
in strange placesn using WD. The 765 was ucoded to do IBM standard formats
so a lot of the who's where is already known and mapped.
>> Things it did do that the WD never had: Multiple seeks or recals, timing
>> for the stepper, head load delay, head settle delay.
>>
>Did it do "implied seeks" wherein the controller looked at where it was and
then
>automatically computed the difference before moving the heads?
No, I know of no chip that did. It made for a peice of that.
>> The biggest difference: register based programming vs command packet to a
>> "port".
>>
>Back in the '77-'82 period I was probably responsible for the use of 100K
>Western chips and it might as well have been decided on a coin toss. I was
No it wasn't, the 765 design was introduced in late '79, by then you were
locked to WD.
>vs packet programming though. Perhaps you could cite an example? The
Western
>part is certainly register based. Isn't the NEC part also just a register
set?
Internally the 765 has "registers". However, you feed it via one port
addres with a
command packet and after the data IO is done you read a status packet of 1-9
bytes
based on the command issued. It's obsious when you look at the part, the
765
has A0 for the port addressing (status and command/data) where A0 only has
meaning{it's only active during /CS not /DACK) during non-dma ops.
>That was an advantage for those who were invested in a software base, but
nobody
>knew that back in '78-79. What's the 36C766? Google comes up empty. I've
seen
>some 37C665/666 types, but 36Cnnn? Who made them?
Several vendors including SMC and UMC. They were variations of the 765 with
rate generators and interface to disk plus IOports (parallel, serial and
even IDE).
Aimed at PCs they replaced the two serial ports, IDE, FDC and parallel
boards.
>What's interesting, BTW, is that even Western, with its institutional
prejudice
>toward analog PLL's went with the 765 core once it went to the fully
integrated
>all-digital FDC, having dealt with the lower data rates in the 1770/72/73
chips,
>which were not shown to be capable of 500 Kbps for some reason. Perhaps
there
>was some advantage in the 765 core that made it more amenable to
integration
>with a digital clock extraction circuit at the higher data rate. I doubt
that
>Intel would have gone for the 765 type if there weren't some manufacturing
>advantage inherent in the silicon. That may be what's made the difference.
>Intel certainly would have chosen the chip that was more economically
>manufacturable, though maybe their primary economy came from the
>already-established relationship (which they'd sabotage later) with NEC.
The 765 core did the step rate and may of the external things that the 1793
needed external hardware for. The preference for digital data seperation
was
pushed by NEC as it could be done with a small 32x4 prom and a latch with
good reliability compared to the often difficult analog designs. Also
digital
fits on silicon of the time better. I have a design and samples we did in
late
'81 to put the floppy side "glue" on one 2500 gate array that allowed for
data
sep, write pre comp, drive and motor selects and all the other things that
would end up on the super chips. The end result was a complete FDC two
chip combo that was half the price of discrete 765 or WD 1793 designs with
no performance compromizes. It was never marketed for obtuse reasons
and less than three years later several vendors were putting 765+glue on
one chip.
And the d7265 wa the ISO 3.5" tuned version that had a shorter VCO sync
time{post index gap time} and a shortend index gap. I believe most of the
765 cores are of the 7265 flavor.
The aside to that is that the SMC 9229 was a digital data sep/clock/precomp
that worked with both the 765 and 1793 with equal perfomance for all rates.
SMC also had a 765 core with analog PLL (9265 or 66) for those that prefered
analog. The 1770/2/3 problem was not data seperator in itself but process
speed
of the die, they{WD} flat out could not do the required 16mhz stuff then for
the
data sep and the other rate generators. The 1793 with external 9229 works
great at 500khz but, the 1793 only has to see something like 2 or 4mhz max
and therein lies the difference.
Allison
> disks for the Bonus Pack. OS/2 Warp Connect version 3 (Blue box,
> includes DOS/Windows support) is on CD-ROM, as is the Bonus Pack. It
> does have two diskettes from which to boot the system for
> installation though. Is there a specific disk(s) that you need to
> replace for Warp 3? I also have OS/2 for Windows version 2.1.
Are the updates still available for this anywhere? For some reason, I'm in
the process of building a PP200 up as an OS/2 system and Warp 3 is the
newest version I've got. (OK, ok, I admit, I'm building it to play
"Galactic Civilizations".) Anyway, I'd kind of like to get it updated to
the current patch level or whatever it's called in OS/2 (been way to long
since I switched to the Mac from OS/2).
Zane
Ben Franchuk wrote:
> What I wanted was a 12/24 bit CPU
I can live with that - 24 bits is really cool from a DSP point of view. 140dB
dynamic
range and you can do two data moves and one arithmetic op with a 24-bit
instruction.
The only modern day 24-bitter that I know of is the Motorola DSP56XX family.
Great for fixed point ( fractional ) number crunching.
> You tell me how I can make $$$ and I will not move to seattle.
> Deal? I could move to Antarctica and make linux boxes. Take a
> penguin and stuff it in old 386. Stamp exported from 'Finland'.:)
I must protest, that's cruelty to penguins. How would you like to be stuffed
into a box labeled Intel or worse still Micro... Damn my keyboards locked up.
How about stuffing old silicon into FPGA's ?
Chris
