I have available a Fluke 9100A and a Fluke 9105A with lots of extra's Pods
deep memory probe keyboard etc..
The 9100A has the newest firmware and a 'new' HD.
The total has to be shipped in two or three boxes or picked up.
I'm located in the Netherlands,
-Rik
So, my UK101 sold for a healthy ?224, which I am very happy about indeed.
However, it's to a buyer in the USA and he wants me to split the
bundle and send just the computer - he does not want the monitor.
He claims that although the computer will run on a 240-to-120V
transformer, the monitor will not, as US DC is 60Hz and European is
50Hz.
Is this correct? It's news to me.
I don't really want to split the package up, TBH - I am not sure that
the monitor is worth much on its own.
--
Liam Proven ? Profile: http://lproven.livejournal.com/profile
Email: lproven at cix.co.uk ? GMail/G+/Twitter/Flickr/Facebook: lproven
MSN: lproven at hotmail.com ? Skype/AIM/Yahoo/LinkedIn: liamproven
Tel: +44 20-8685-0498 ? Cell: +44 7939-087884
Hey Sander,
> Pah, X-Copy (http://www.youtube.com/watch?v=TCDtnQiZlSc) .... D-Copy
> (http://www.youtube.com/watch?v=gUT-gnwpLJ0) FTW! :)
Yes, there were many of clones. But I think it's fair to say that many of them just copied the feature set of White Lightning and Fast Lightning which later became X-Copy. The beast of the package was always Cyclone, which with the help of the hardware adapter shifted the read line to the write line. The problem was the missing precomping and refreshing of bit cells, but this was the best you could get back in the day.
http://www.youtube.com/watch?v=o2T9qpE6Jhw
The inventor of Cyclone, Rich Aplin, actually invented KryoFlux in 2008, about 20 years after the original was made for the Amiga. :-)
http://www.youtube.com/watch?v=pOiWGj3A6Eg
Enjoy.
Hi Jim,
> Not relevant to the archival media question. If I want to go out x # of
> years and work with what you are using a comparables, they certainly
> stand an excellent chance of being in the state of being useful (jpgs,
> pdfs, word files, (sorry word and MS are like cockroaches, they'll
> never go away).
This is not about the tools, the formats matter. You need to have well defined formats that are fully documented and open to make sure you can extract the data in the future. I don't know if I'll be using Photoshop in a decade, it matters if I can still open my JPEGs (problematic if you look at the reduction involved) or TIFFs or WAVs or FLACs.
It does not matter if you like MS or don't like them. The word format itself is documented, so as long as this documentation is preserved, all is fine. That's why the data we preserve is in containers that have proven to be suitable for over a decade now, they are documented and / or available with source, so people can see how the encoding works.
Chris
On 3/1/12, paisley at erols.com <paisley at erols.com> wrote:
>
> I was able to get two H960 racks (Thanks Doc!) and what I am looking for now
> are the brackets that connect 2 racks together. Does any one have any of
> these? Or have a photo of what one looks like? Thanks.
If you pull off the side panels where you want to do the join (lift up and out), 1/4" bolts and nuts will join the racks together at 4 places.
This lacks any beige fillers (which is I think maybe what you're asking for) but it makes two new side panels that maybe can be used elsewhere.
Tim.
Hi Fred!
>> We don't have anything to hide. We do have eleven years of field
>> experience in regard to preservation.
> Even "post-millenium" newcomers are very welcome!
>
> Glad to have y'all involved.
>
>
Thanks for the warm welcome. It's nice to see all the dinosaurs still
around. I didn't count in e.g. my years at Cachet (X-Copy, Amiga) in the
early 1990s as that was not preservation but banging bits from the
source to the target. So if we/I still qualify as newcomers... fine with
me. Enjoy!
Looking for early TRSDOS disks (pre-2.0) for the TRS-80 Model II.
This would be on 8-inch disks. This is NOT the same as any TRSDOS for
the Model I or Model III.
Thanks!
Eric
Hi Dave,
answers below. I must admit I was not expecting this in a thread with
this title, but I spotted it because I had replied the other day. I hope
I can address all your questions.
Best,
Chris
Am 29.02.2012 15:00, schrieb cctalk-request at classiccmp.org:
>
> I do have a Kryoflux board too ? I got it mainly for testing purposes.
> The Kryoflux team does not seem interested in working together with
> interested people at the same level as Phil ?
Are we? In fact many people working on KryoFlux are contributors.
Several people work with the source, and we recently even visited a KEEP
(http://www.keep-project.eu/ezpub2/index.php) workshop to discuss and
exchange with others, to name just one occasion. I never got a request
or proposal from you, but if you have ideas or comments, or whatever to
share... please let us know!
If you want to browse our website... there is a ton of information we
shared (and still do) over the last decade.
> their actually-useful
> analysis software is very expensive and even dongle protected,
> according to the FAQ at
> http://forum.kryoflux.com/viewtopic.php?f=3&t=3#p1241 .
Yes it is, so are many products. It must admit I don't get how this is
related to KryoFlux, or us being interested?
I have several products from the same company, some are cheap, others
are more expensive. Some come with a dongle, others activate only
(yikes!). People that want it can contact us. Some did/do. And some use
the software as part of a special arrangement. I really don't see why
this is wrong.
> The basic DTC
> software is closed-source and can be rather temperamental, as is the
> firmware.
Is it? I'd be happy to hear about quirks. I in fact have many posts and
mails that report the opposite. People are in fact happy it works so
well. If anything is broken, please send in a bug report. I haven't seen
one and I really wonder about the firmware. How would one notice that
it's currently "temperamental"?
I wonder what this has to do with the status of the source. I'd say it
does say nothing about quality. I in fact know many quality products
that are not open but I think they are very well executed. Does that
mean being open but flawed would be more desireable?
> Though Christian says the Kryoflux "never had such a
> problem," I have never seen an independent analysis or source code or
> anything confirming that.
We don't have anything to hide. We do have eleven years of field
experience in regard to preservation. The problem outlined by Johannes
was a design fault, it's not a glitch. You must not have ambiguity in
encoding. Apparently it was fixed lately, a year after release.
> I may end up doing this myself. Without
> source it's definitely more work to verify it.
Let me know how we can help you.
It feels a bit odd to read the above when in fact you never asked for
anything of the above. How should we know you would want to audit it?
> An overview of the engineering of the Kryoflux board indicates it was
> designed mainly with low cost in mind. The level buffers on it are
> very ESD-sensitive and are not designed for cables (so a long floppy
> cable may cause issues), and there's lack of protection overall,
> especially in the power supply.
I think this is very easy to explain... it was made to be as cheap as
possible without sacrificing ingestion quality. We like to make it
affordable, and we'd even make it cheaper if we could. We don't want it
to be more expensive. The buffers work very well, and we haven't had a
single dead one in more than 600 units sold. In regard to protection:
One dead board in 600 units supplied, the PSU was broken and just fried
the board. We exchanged it. Should I have made all 600 more expensive to
cover that one case? That's 599 vs 1. And again: We don't have to hide
anything - so I am telling you here in public.
> There's no way the current Kryoflux design ever will be able
> to image high-RPM media.
That's correct. The software could, but the hardware defnitely can't. We
never targeted harddrives. We focussed on one specific field of use. And
it's working very well. If we'd want to do harddrives or other high-RPM
media, we would do another model or product.
If these things were cars... we wanted to make something that drives,
not something that floats or flies. Just one thing... but very well
executed.
> As for Linux support: I've seen several complaints lately on the
> Kryoflux forums about libusb and glibc issues.
Right, you did not want to mention that this is more or less a
"theoretical problem"? We offer 32bit and 64bit builds. The 32bit worked
for all users (as far as I know, and also on 64bit systems), the 64bit
version needed to be refined to make it work on as many distributions as
possible. That's just the way it is with binaries on Linux. I am not
really happy with that.
But on the other hand it satisfies many customers. Just install the
software, attach the board - have fun. Buying a bread instead of always
baking your own isn't that bad.
I wonder how many users will be able to compile a source on Windows or
Mac, just to shed some light on the other side of the coin. It's not all
black and white.
> Take a look:
> http://forum.kryoflux.com/viewforum.php?f=3 . Even though they're
> somewhat responsive, it's still relying on them for support.
I don't get the meaning of this but... if you mean we need a bug report
to remove a bug... yes, we do. The wording "somewhat responsive" makes
me wonder... people usually get replies the next working day, and even
fixes come along pretty quickly. What is wrong with that? To make it
better, we have to listen. We do.
> There's also the issue of the Kryoflux software lagging behind.
> Currently the Mac version (which is what I use) is a few months old,
> and lacks many of the features I would like.
That is true, you would have to use Windows or Linux. Today.
> When I asked about this,
> I got brushed away, saying that the person who usually builds that
> version is busy.
Excuse me, would you mind publishing the answer I gave you as well? I
wonder where I did brush you away. I think I was very polite and
explained that the Mac port was being worked on. And yes, it's true, our
Mac devs are very busy, which is why the team was expanded and a new
release is near completion.
We welcome everyone that needs an earlier port to step forward and help.
Sometimes it's just diffing some files and applying a few platform
specific changes. Still, it needs to be done with care and by someone
who knows what he's doing. We take quality very serious.
Does anyone have a Operator's Field Reference Guide (or any other
manual) for an Atlantic Research Interview Comstate 1?
--
Pete Peter Turnbull
Network Manager
University of York
> From:?ard at p850ug1.demon.co.uk (Tony Duell)
> Subject:?Re: UK versus US monitor question
>> > > It used to be the case that TVs synced to the mains
>> > frequency but I don't
>> >
>> > Was it?
>>
>> A long time ago...
>
> OK, I am sceptical. ?What do you mean by a 'long time ago'?
>
> Unti lthe coming of the National Grid, different areas would be supplied
> with mains at slightly differnet frequencies (even assuming it was
> supposed to be nominally 50Hz), and therre would eb no phase relationship
> at all. So usign that for any form of TV synchronisation is a non-starter.
>
> So that really limits us to post-WW2 TVs. The oldest book of schematics I
> have is dated 1953, but it contains models going back to 1948. Not one
> attempts to derrive the vertical sync signal from the mains as far as I
> can see.
>
> But I am a scientist... So while I have not found such a TV, I ?an't say
> they don't exist. So I would ask you to state the make and model of one
> or more TVs that derrived the vertcal sync signal from the mains, so that
> I can track down the scheamtics and see what they did.
>
> -tony
There is a schematic from 1930 on this WWW page from our local museum.
http://www.newsm.org/Wireless/TV/mechanical_TV.html
Click on the link for the booklet "The Romance and Reality of Television".
--
Michael Thompson
Original Message:
Date: Sat, 25 Feb 2012 19:15:37 +0000 (GMT)
From: ard at p850ug1.demon.co.uk (Tony Duell)
> > IIRC tjhat switchbox contains what we (in the UK) call a 'Balun'. I am
> > not sure if that term has crossed the Pond, it's an abreviation of
> > 'Balanced <-> Unbalanced'.
>
> In the US, the term "balun" is not used by the general public. It's used
Ove here, the 'genral public' wouldnt' know what a matching transformer
was used for :-)
-----
Not just the general public; when one of my tenants had cable TV installed
recently the installer told her that she'd have to buy a new second TV
because her perfectly good 300-Ohm-only TV was not compatible with the coax
>from the converter box...
Piotr,
I had problems with my KA694 system at first, I reseated all the
cards including
the power supply and problems went away.
Dan
On Wed 02/29/12 8:42 AM , VCOMP vcomp99 at gmail.com sent:
Dan,
On 02/26/2012 05:46 PM, Daniel Snyder wrote:
> Piotr,
>
> Found the KA694 maintenance manual. Looks as though powerup tests
must
> finish
> to the console prompt in order to perform a firmware upgrade. What
> number do
> the tests freeze at?
>
> Below is a normal powerup sequence:
>
> KA694-A V2.4, VMB 2.15
> Performing normal system tests.
> 70..69..68..67..66..65..64..63..62..61..60..59..58..57..56..55..
> 54..53..52..51..50..49..48..47..46..45..44..43..42..41..40..39..
> 38..37..36..35..34..33..32..31..30..29..28..27..26..25..24..23..
> 22..21..20..19..18..17..16..15..14..13..12..11..10..09..08..07..
> 06..05..04..03..
> Tests completed.
> Loading system software.
> (BOOT/R5:0 DIA0)
>
> I have looked on Google for the firmware file, did not find it.
> Maybe try the comp.sys.dec or comp.os.vms newgroups for
> answers. I even looked in some old Condists for the file.
> Someone who came from DEC field service may be able
> to provide a solution.
>
> Dan
Thank you for your help and hints - I'll try to ask at c.s.d. and
c.o.v.
As for the boot problems - during startup, system tests are stoping
in
different stage - sometimes I see first two lines, sometimes I see
nothing except 'Performing normal system test' and sometimes it
hangs
after all tests complete... It's very strange, and the firmware is
my
first suspect. Unfortunately, I don't have spare CPU card so I can't
verify what is the real problem...
Regards,
Piotr
Hi All
For some time now, I'm a happy owner of a VAX 4000-705 system.
Unfortunately, it came with corrupted firmware, and I don't have
replacement KA694... In 'KA694 CPU System Maintenance' I found
information that there were FEPROM updates distributed (AFAIK it was
called Firmware Update Utility). Can someone on this list point me to a
source for that? Or at least the firmware image alone?
TIA,
Piotr
I have been scanning and OCRing BYTE magazines, and so far have a stack two feet tall of magazines which have been de-spined with a large paper cutter.
Dates are from 1978 to 1987 - not all issues are present.
They are free to anyone who wants to pick-up or pay shipping.
They are in southern California, Orange County, 92656
I have half as many which have NOT been de-spined, and are intact - someone else has already scanned those issues, so I won't cut up mine, but will still give them away - nothing earlier than 1980 though.
Steve.
On Fri, 17 Feb 2012 22:17:17 +0000 (GMT), ard at p850ug1.demon.co.uk (Tony
Duell) wrote:
> A few comments...
>
> 1) I can find nothing to suggest that this has anythign to do with the
> UK. The televisoin company is not a UK one (AFAIK), and while is at least
> one small village in England called Melbourne, I cna't beleive it had
> much of a hacker./cracker community.
They are based in Sydney and Melbourne, Australia. They must mean
Melbourne, Australia.
/Jonas
Hi Johannes,
I can assure you there has never been a problem like this with KryoFlux.
Our devs work in software engineering for large companies (e.g. console
hardware and games, chances are you already own a device that has code
made by one of us) and are trained to the latest standards. Even dumps
made with the very first public beta are valid in regard to data
integrity and there is no need to redump anything. There are hundreds of
units out in the field, some at large institutes and libraries, where
they are being used daily. It's a device made by preservationists for
preservationists.
For the record: KryoFlux' counters are 32 bits wide. This is no hardware
limitation, it was just chosen as sufficient, but we could as well move
to 64 if needed.
I would recommend our forums at http://forum.kryoflux.com/ which should
give you an impression about user satisfaction. We recently added ADF
writing, with more formats to follow.
Best,
Chris
Am 27.02.2012 19:00, schrieb cctalk-request at classiccmp.org:
> Has anyone heard of problems with Kyroflux?
I remember taking a copy of NewDos 2.1+ , and an issue of 80-Micro to my local Radio Shack and using their Model I to apply zaps to the OS to speed up the boot and step speed. The store manager thought I was crazy, but it worked great! There were also zaps for TRS-DOS 1.3 which I applied to a copy of that, and made copies for the store.
They gave out the faster TRS-DOS to all their disk drive sales as a way to enhance the sale. By that time, the drives were all Tandon TM-100's and could easily handle 12ms stepping. I think I also applied the 40 track patch as well.
Al Hartman
From: Eric Smith <eric at brouhaha.com>
On 02/26/2012 01:56 PM, Fred Cisin wrote:
> One of the things that I remember about Apparat (slightly before that)?
> was that NewDOS (was it only in NewDos80, or all the way back to?
> APRDOS?) gave the user the capability to set the step time, to be able?
> to take advantage of the 5ms step time of the Tandon, etc. drives,?
> rather than have to always step everything at 40ms to be able to?
> handle the original SA400 (the original drive shipped with TRS80).?
IIRC, NEWDOS/80 allowed the step rate to be changed on a per-drive basis?
using the PDRIVE command. In fact, you could change an amazing number of?
parameters for the drive or the filesystem format using that command.
I don't think NEWDOS had such a command, though there might have been?
ZAPs (patches) to change the step rate globally.|
Hello,
Does anyone have access to a Murata databook from the 1998 - 2004 time
frame? I'm looking for a datasheet for a particular part and have not
been able to find anything online.
Please contact me off-list. Thanks!
Cheers,
Dan
dan at decodesystems.com
I don't know what was the slowest, but I suspect u can get by with what was
the slowest defacto industry standard as default and not worry about anyone
who was faster.
As I recall Shugart dominated the 8 and 5? inch FDs and they were not
buffered. So your step rates from their specs are
SA800 ? 8 msec
SA400 ? 40 msec
SA400L ? 20 msec
I believe most of the 3? did use buffered seek and I would get the Sony
spec, not the first Sony but the one that complied with the MIC standard
cartridge spec. Sony may have adopted the Shugart spec, which was:
SA300 Unbuffered ? 6 msec
SA300 Buffered ? 50 usec minimum period; 1 usec minimum pulse width
The SA1000 8-inch HDD from a secondary source apparently can accept buffered
pulses at a 1.0 u sec min spacing.
The ST506 OEM manual is at Bitsavers; it was unbuffered only at 3 msec
minimum period, 10 usec minimum pulse width. (there was a hidden internal
second pulse generated at 2.8 msec)
The ST412 specification [Apr 82] was one Seagate buffered mode
implementation that most everyone had to follow
ST412 Unbuffered ? 3 msec
ST412 Buffered ? 25 usec minimum period; 200 usec maximum period, 2.0 usec
minimum pulse width
Microprocessor utilization on the ST412 adds the capability of capturing and
storing up to 305 step pulses. The controller may burst pulses to the 412
and they will be accepted until 1) time after last pulse exceeds 200 usec or
2) 305 step pulses are received. At the occurrence of either of these
conditions, the ST 412 microprocessor will stop accepting step pulses from
the controller and will begin issuing them to the stepper motor. Depending
on the length of seek, the microprocessor will select the optimum algorithm.
Any pulses issued at a rate between 200 usec and 3 msec may be lost.
Note the subsequent ST212 (Apr 84) has a buffered spec of 5 usec min, 500
usec max with a 2 usec min pulse width.
So I would set my defaults
Unbuffered FDD seek ? 40 msec
Buffered FDD seek ? not supported
Unbuffered HDD seek ? 6 msec
Buffered HDD Seek ? 25 usec period with a 2 usec pulse
Good luck
Tom
> From: classiccmp at philpem.me.uk
>
> Hi guys,
>
> Does anyone know what the typical range of floppy and ST506/ST412 drive
> track-to-track seek rates is?
>
> I'm finding myself having to modify the seek logic in the DiscFerret to
> accommodate the Seagate ST-277R RLL drive, which requires that
> buffered-seek pulses be spaced between 8 and 200 microseconds apart. Any
> more than that and it assumes you're doing a 'slow' seek at 10ms per
> step.
>
> At the moment the DiscFerret's step rates are set up in 250us intervals,
> with an 8-bit divider register. Seek rates can be between 250
> microseconds and 64 milliseconds in this configuration.
>
> Feeding the ST277R the 250us step pulses... really screws it up. The
> drive deasserts READY and SEEK-COMPLETE and seems to freeze up
> completely. Hardly unexpected...
>
> If I change the seek clock to 125us, I get a minimum of 125us and a
> maximum of 32ms using the same divider.
>
> Is 32ms likely to be enough for even the slowest drives?
>
> Out of curiosity, does anyone know what the slowest-seeking floppy drive
> or MFM/RLL hard drive ever made was, and what its track-to-track seek
> rate was?
>
> Thanks,
> --
> Phil.
> classiccmp at philpem.me.uk
> http://www.philpem.me.uk/
Hi guys,
Does anyone know what the typical range of floppy and ST506/ST412 drive
track-to-track seek rates is?
I'm finding myself having to modify the seek logic in the DiscFerret to
accommodate the Seagate ST-277R RLL drive, which requires that
buffered-seek pulses be spaced between 8 and 200 microseconds apart. Any
more than that and it assumes you're doing a 'slow' seek at 10ms per step.
At the moment the DiscFerret's step rates are set up in 250us intervals,
with an 8-bit divider register. Seek rates can be between 250
microseconds and 64 milliseconds in this configuration.
Feeding the ST277R the 250us step pulses... really screws it up. The
drive deasserts READY and SEEK-COMPLETE and seems to freeze up
completely. Hardly unexpected...
If I change the seek clock to 125us, I get a minimum of 125us and a
maximum of 32ms using the same divider.
Is 32ms likely to be enough for even the slowest drives?
Out of curiosity, does anyone know what the slowest-seeking floppy drive
or MFM/RLL hard drive ever made was, and what its track-to-track seek
rate was?
Thanks,
--
Phil.
classiccmp at philpem.me.uk
http://www.philpem.me.uk/
>
> > > > It used to be the case that TVs synced to the mains
> > > frequency but I don't
> > >
> > > Was it?
> >
> > A long time ago...
>
> OK, I am sceptical. What do you mean by a 'long time ago'?
>
> Unti lthe coming of the National Grid, different areas would be supplied
> with mains at slightly differnet frequencies (even assuming it was
> supposed to be nominally 50Hz), and therre would eb no phase relationship
> at all. So usign that for any form of TV synchronisation is a non-starter.
>
> So that really limits us to post-WW2 TVs. The oldest book of schematics I
> have is dated 1953, but it contains models going back to 1948. Not one
> attempts to derrive the vertical sync signal from the mains as far as I
> can see.
>
>
I'm not sure why I'm getting into this, seeing as I know little about it.
However...
Perhaps studio sync sources were derived from mains power at one time purely
as a method of picking a reference to use so that there would be minimal
picture roll when transmission output is switched between different sources?
Maybe this was found to be counterproductive when large changes in load caused
momentarty variations in frequency even though the electricity producers worked
to average these out in the longer term?
(I don't have any guesses as to what might have been used for a line sync
source.)
If a three phase grid system is in use with individual receivers normally
connected to single phase supplies derived from it and having no choice as to
which phase they ended up getting powered by, it would seem to be rather
more difficult to attempt to use the power supply waveform as a sync source for
reception than to use the sync pulses present in the transmission.
Regards,
Peter Coghlan.
Hello all!
I have been reading this list some time now. I have a Atari 8 + 16bit collection with hundreds floppies 5.25 and 3.5. I followed the post here about disk imaging and have seen Discferret and Kyroflux. Both look good to me but I use Linux so like the idea of getting a Discferret because its open source. However I found:
http://www.fpgarelated.com/usenet/fpga/show/105048-1.php
To me this looks Discferret has a problem with either race condition (pulse lost) or ambiguity (two encodings meaning same) and to me this looks this problem is valid for all dumps already made. I talked to other guys from engineering classes and one suggest using 12bits (instead of 8) for counter but this would mean having to few RAMs on the board. Does that mean to better not get a Discferret? Has anyone heard of problems with Kyroflux?
Want to start making images soon.
Greetings
-- Jo
Hi all,
several weeks ago someone asked for a Z80 BASIC, and my recommendation was
the 12K Extended BASIC from TDL. I got several offline queries where to
obtain
this.
I myself knew of a hex dump in a German Book (published there for academical
and amateur purposes "because the company does not exist anymore"; the
book was
>from 1982). Under this premise I disassembled the hex dump and commented
(almost) all code. I'll make this commenting work available to anyone
who is interested.
I don't publish it on a web page (I don't think I need one), but since
the disassembly and
my comments are CC-BY-SA, anyone else may feel free to do so. Send me a
request
offline to receive a ZIP file (86k) with the listing and the hex dump.
--
Holger
Does anyone here have any experience with using automated tools to convert
Delphi source code to C++? I'm trying to convert a Delphi thing for
Windows that does little more than spit a firmware image out a serial
port into plain C and I'm not making much sense of the Delphi code.
--
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?