[cctalk] Re: Greaseweazle part 2
Still trying to make sense of this thing. The problem is that one very important thing is missing. I refer to DODUMENTATION. I don't fall for this modern rubbish that a product with a thin manual is easy to use. No, the thicker the manual the better. It will probablt answr my questions. But the Greaseweazle has no documentation at all other than the built-in help, (which is what I'd expect, a reminder of the options if you know the product and can't remember the exact term used to, say, check the drive speed). If I type 'gw' at a command prompt I get the following, which at least gives the options. -- C:\classic_computer\greaseweazle\greaseweazle-1.13>gw Usage: gw [--time] [action] [-h] ... --time Print elapsed time after action is executed -h, --help Show help message for specified action Actions: infoDisplay information about the Greaseweazle setup. readRead a disk to the specified image file. write Write a disk from the specified image file. convert Convert between image formats. erase Erase a disk. clean Clean a drive in a zig-zag pattern using a cleaning disk. seekSeek to the specified cylinder. delays Display (and optionally modify) drive-delay parameters. update Update the Greaseweazle device firmware to latest (or specified) version. pin Change the setting of a user-modifiable interface pin. reset Reset the Greaseweazle device to power-on default state. bandwidth Report the available USB bandwidth for the Greaseweazle device. rpm Measure RPM of drive spindle. - I can basically understand that So lets see how to write an image to a disk . I type gw write -h and get : - C:\classic_computer\greaseweazle\greaseweazle-1.13>gw write -h usage: gw write [options] file Write a disk from the specified image file. positional arguments: file input filename options: -h, --help show this help message and exit --device DEVICE device name (COM/serial port) --drive DRIVEdrive to read (default: A) --diskdefs DISKDEFS disk definitions file --format FORMAT disk format --tracks TSPEC which tracks to write --pre-erase erase tracks before writing (default: no) --erase-emptyerase empty tracks (default: skip) --fake-index SPEED fake index pulses at SPEED --no-verify disable verify --retries N number of retries on verify failure (default: 3) --precomp PRECOMPwrite precompensation --dd DD drive interface DD/HD select (H,L) DRIVE: Drive (and bus) identifier: 0 | 1 | 2 :: Shugart bus unit A | B :: IBM/PC bus unit SPEED: Track rotation time specified as: rpm | ms | us | ns | scp | TSPEC: Colon-separated list of: c=SET :: Set of cylinders to access h=SET :: Set of heads (sides) to access step=[0-9] :: # physical head steps between cylinders hswap :: Swap physical drive heads h[01].off=[+-][0-9] :: Physical cylinder offsets per head SET is a comma-separated list of integers and integer ranges e.g. 'c=0-7,9-12:h=0-1' FORMAT options: acorn.adfs.160acorn.adfs.1600 acorn.adfs.320 acorn.adfs.640acorn.adfs.800acorn.dfs.ds acorn.dfs.ss akai.1600 akai.800 amiga.amigadosamiga.amigados_hd atari.90 atarist.360 atarist.400 atarist.440 atarist.720 atarist.800 atarist.880 coco.decb coco.decb.40t coco.os9.40ds coco.os9.40ss coco.os9.80ds coco.os9.80ss commodore.1541commodore.1571commodore.1581 dec.rx01 dec.rx02 dragon.40ds dragon.40ss dragon.80ds dragon.80ss ensoniq.1600 ensoniq.800 ensoniq.mirage gem.1600 ibm.1200 ibm.1440 ibm.160 ibm.1680 ibm.180 ibm.2880 ibm.320 ibm.360 ibm.720 ibm.800 ibm.dmf ibm.scan mac.400 mac.800 mm1.os9.80ds.hd32spt mm1.os9.80ds.hd36spt msx.1d msx.1dd msx.2dmsx.2dd occ1.dd occ1.sd olivetti.m20 pc98.2d pc98.2dd pc98.2hd pc98.2hs raw.125 raw.250 raw.500 sci.prophet sega.sf7000 tsc.flex.dsdd tsc.flex.ssdd zx.trdos.640 Supported file suffixes: .a2r .adf .ads .adm .adl .d64 .d71 .d81 .d88 .dcp .dim .dsd .dsk .edsk .fdi .hdm .hfe .ima .img .imd .ipf .mgt .msa .raw .sf7 .scp .ssd .st.td0 .xdf And this is where I get lost.. What are all the file suffixes (extensions?) Does the program determine the file type from that?What does each
[cctalk] Re: Any RSX-11 fans able to identify file types?
On 6/24/23 12:38, Wayne S wrote: > Chuck, why not post the catalog snd we’ll all take a look? > Power of the internet! Okay, I guess that's okay. Here's the data from the MFD: https://icedrive.net/s/Q56ZY2Sv4g62Gi9vZ9jzNQ2CD6Bu Since this is customer data, I can't publish the contents of the files themselves. Does anyone recognize this stuff? --Chuck
[cctalk] Re: Any RSX-11 fans able to identify file types?
Chuck, why not post the catalog snd we’ll all take a look? Power of the internet! Sent from my iPhone > On Jun 23, 2023, at 18:58, Chuck Guzis via cctalk > wrote: > > I've got a few backup sets (potentially incomplete) done on MicroRSX > that were created with BRU on RX50 media. I've cranked out some code to > itemize the contents, but the file types are a mystery. I suppose that > one has to live in that world to know (e.g. MSL) > > The sets appear to be (parts) of an incremental backup scheme; I think > I've got at least one copy of the complete set. > > Would anyone be willing to have a look at the (ASCII) file catalog and > suggest the application that may have created the files? > > Email me offlist if interested. > > --Chuck
[cctalk] Re: PCs Limited XT
I think that the tubo mode is not happening, it's running like a regular XT. I have seen it go into Turbo mode once or twice, so there is a marginal chip somewhere that needs to be replaced. That's my final decision. Either way, I have filled the hard drive up with various software from the time period and put it out for people to use in the museum. If you're in the south-eastern PA area, feel free to stop by and check it out. The PC Limited machine from the VCForum I think is the same one as this one. I think the guy gave up on it and donated to the museum. It needed a new power supply, hard drive controller, disk drive to get it running again. I put MS DOS, removed the botched IBM DOS someone had attempted to load. Really, you're right. It's just a cheap clone, but it's a cheap clone that happens to be one of the first PCs made by what would become Dell Computer, worth saving and keeping running! B On Sat, Jun 24, 2023 at 1:36 PM John Herron via cctalk < cctalk@classiccmp.org> wrote: > On Fri, Jun 23, 2023, 6:59 PM Bill Degnan via cctalk < > cctalk@classiccmp.org> > wrote: > > > On Fri, Jun 23, 2023, 6:33 PM Fred Cisin via cctalk < > cctalk@classiccmp.org > > > > > wrote: > > > > > On Fri, 23 Jun 2023, Bill Degnan via cctalk wrote: > > > > It boots fine, did I say it did not boot? I don't remember. There > is > > no > > > > arcnet card, it's not the later model PCs LIMITED box, does not match > > the > > > > red label logo that came out in 1986 > > > > > > Well, I appreciate that people answered my question. I sometimes ask > > questions and then proceed to work on it until I figure it out. There > is a > > THESYS "MULTI/RAM card and that was the card with the password ROM. I > > found the dip switch "PW" and turned it off. Problem solved. The Turbo > > error #04 is still a mystery, but it does not prevent me from using the > > system. I am thinking there's an incorrect but incidental switch > setting. > > It could be a RAM chip but I have no proof. Chkdsk returns an full 640K. > > > > I'm very curious if it gets figured out or if there are any publications > maybe around the time to help identify the parts Dell would have used. I > could be thinking too simply for the college years he built them in his > dorm so I'd imagine common off the shelf parts and generally just an IBM > clone. I would think some other similar era computers would also have that > error code. > > I started reading another person's post with a similar error on vcfed > forums but I don't think they ever really solved it. There was an attempt > to dump the bios to see what it might be checking (beyond my depth of > knowledge). > > I guess that would let you know if it's a bios or other device printing > the error. I assume you've booted it with no addon cards and still see the > message. > > > >
[cctalk] Re: PCs Limited XT
On Fri, Jun 23, 2023, 6:59 PM Bill Degnan via cctalk wrote: > On Fri, Jun 23, 2023, 6:33 PM Fred Cisin via cctalk > > wrote: > > > On Fri, 23 Jun 2023, Bill Degnan via cctalk wrote: > > > It boots fine, did I say it did not boot? I don't remember. There is > no > > > arcnet card, it's not the later model PCs LIMITED box, does not match > the > > > red label logo that came out in 1986 > > > Well, I appreciate that people answered my question. I sometimes ask > questions and then proceed to work on it until I figure it out. There is a > THESYS "MULTI/RAM card and that was the card with the password ROM. I > found the dip switch "PW" and turned it off. Problem solved. The Turbo > error #04 is still a mystery, but it does not prevent me from using the > system. I am thinking there's an incorrect but incidental switch setting. > It could be a RAM chip but I have no proof. Chkdsk returns an full 640K. > I'm very curious if it gets figured out or if there are any publications maybe around the time to help identify the parts Dell would have used. I could be thinking too simply for the college years he built them in his dorm so I'd imagine common off the shelf parts and generally just an IBM clone. I would think some other similar era computers would also have that error code. I started reading another person's post with a similar error on vcfed forums but I don't think they ever really solved it. There was an attempt to dump the bios to see what it might be checking (beyond my depth of knowledge). I guess that would let you know if it's a bios or other device printing the error. I assume you've booted it with no addon cards and still see the message. >
