[M100] DVI compatible drives
Epson SD-521 works in a DVI.
Re: [M100] new project
ah, so in some cases it would be good to have REX restore the date too. On Wed, Nov 1, 2017 at 8:53 AM, Brian Brindle wrote: > Stephen, yes - that works perfectly. The situation I was describing above > is after a CTRL-BREAK-RESET total wipe of the M100 after I have wedged it > completely - then reload RAM from REX. > > > On Wed, Nov 1, 2017 at 8:43 AM, Stephen Adolph > wrote: > >> At some point in REX I included a feature to maintain clock setting >> through ram image swaps. >> >> On Wed, Nov 1, 2017 at 8:21 AM, Brian Brindle wrote: >> >>> Peter, >>> >>> The current clock in the M100 does just fine usually. Unless it sits for >>> a long time. My request for another one is just me being lazy. (sort of). >>> >>> I use my m100 in strange ways and often I have issues where it crashes >>> or locks up and requires a total system reset. >>> Most of my activities with it require accurate time. I'm either logging >>> things, tracking things or just doing notes etc. >>> With REX it's like a dream to recover from these situations. Granted, >>> more times than not REX is also the cause.. >>> >>> But right now I reset, load REXMGR, reload the RAM image and it takes >>> seconds. >>> >>> Then I have to set the clock by either going into BASIC and setting the >>> 3 variables or attaching one of my external devices >>> and running a basic program to do it for me. >>> >>> Not hard mind you but when I do this same thing in VirtualT the time is >>> always right so maybe I'm spoiled. >>> >>> >>> Brian >>> >>> >>> >>> >>> On Oct 31, 2017 7:01 PM, "Peter Vollan" wrote: >>> >>> Let me sure that I understand: however correctly you set the time on >>> your Model 100, it will "drift off", because it cannot keep correct >>> time? >>> >>> >>> On 26 October 2017 at 12:58, John R. Hogerhuis wrote: >>> > >>> > >>> > On Thu, Oct 26, 2017 at 12:22 PM, Brian Brindle >>> wrote: >>> >> >>> >> Hey John, >>> >> >>> >> To move RAM images around I"m using REX, creating a backup of the RAM >>> >> image and saving it to "disk" or in this case Mcomm or my NADS. I >>> like Mcomm >>> >> because the directory it saves everything in on the phone is >>> automatically >>> >> backed up (by another application) to dropbox right now. Then I load >>> that >>> >> image in VirtualT on the PC. >>> >> >>> > >>> > Ah. Well, I did write a program to sync time with NADSBox. >>> > >>> > http://bitchin100.com/wiki/index.php?title=Synchronize_Time_ >>> with_your_NADS >>> > >>> > -- John. >>> >>> >>> >> >> >
Re: [M100] new project
Stephen, yes - that works perfectly. The situation I was describing above is after a CTRL-BREAK-RESET total wipe of the M100 after I have wedged it completely - then reload RAM from REX. On Wed, Nov 1, 2017 at 8:43 AM, Stephen Adolph wrote: > At some point in REX I included a feature to maintain clock setting > through ram image swaps. > > On Wed, Nov 1, 2017 at 8:21 AM, Brian Brindle wrote: > >> Peter, >> >> The current clock in the M100 does just fine usually. Unless it sits for >> a long time. My request for another one is just me being lazy. (sort of). >> >> I use my m100 in strange ways and often I have issues where it crashes or >> locks up and requires a total system reset. >> Most of my activities with it require accurate time. I'm either logging >> things, tracking things or just doing notes etc. >> With REX it's like a dream to recover from these situations. Granted, >> more times than not REX is also the cause.. >> >> But right now I reset, load REXMGR, reload the RAM image and it takes >> seconds. >> >> Then I have to set the clock by either going into BASIC and setting the 3 >> variables or attaching one of my external devices >> and running a basic program to do it for me. >> >> Not hard mind you but when I do this same thing in VirtualT the time is >> always right so maybe I'm spoiled. >> >> >> Brian >> >> >> >> >> On Oct 31, 2017 7:01 PM, "Peter Vollan" wrote: >> >> Let me sure that I understand: however correctly you set the time on >> your Model 100, it will "drift off", because it cannot keep correct >> time? >> >> >> On 26 October 2017 at 12:58, John R. Hogerhuis wrote: >> > >> > >> > On Thu, Oct 26, 2017 at 12:22 PM, Brian Brindle >> wrote: >> >> >> >> Hey John, >> >> >> >> To move RAM images around I"m using REX, creating a backup of the RAM >> >> image and saving it to "disk" or in this case Mcomm or my NADS. I like >> Mcomm >> >> because the directory it saves everything in on the phone is >> automatically >> >> backed up (by another application) to dropbox right now. Then I load >> that >> >> image in VirtualT on the PC. >> >> >> > >> > Ah. Well, I did write a program to sync time with NADSBox. >> > >> > http://bitchin100.com/wiki/index.php?title=Synchronize_Time_ >> with_your_NADS >> > >> > -- John. >> >> >> > >
Re: [M100] new project
At some point in REX I included a feature to maintain clock setting through ram image swaps. On Wed, Nov 1, 2017 at 8:21 AM, Brian Brindle wrote: > Peter, > > The current clock in the M100 does just fine usually. Unless it sits for a > long time. My request for another one is just me being lazy. (sort of). > > I use my m100 in strange ways and often I have issues where it crashes or > locks up and requires a total system reset. > Most of my activities with it require accurate time. I'm either logging > things, tracking things or just doing notes etc. > With REX it's like a dream to recover from these situations. Granted, more > times than not REX is also the cause.. > > But right now I reset, load REXMGR, reload the RAM image and it takes > seconds. > > Then I have to set the clock by either going into BASIC and setting the 3 > variables or attaching one of my external devices > and running a basic program to do it for me. > > Not hard mind you but when I do this same thing in VirtualT the time is > always right so maybe I'm spoiled. > > > Brian > > > > > On Oct 31, 2017 7:01 PM, "Peter Vollan" wrote: > > Let me sure that I understand: however correctly you set the time on > your Model 100, it will "drift off", because it cannot keep correct > time? > > > On 26 October 2017 at 12:58, John R. Hogerhuis wrote: > > > > > > On Thu, Oct 26, 2017 at 12:22 PM, Brian Brindle > wrote: > >> > >> Hey John, > >> > >> To move RAM images around I"m using REX, creating a backup of the RAM > >> image and saving it to "disk" or in this case Mcomm or my NADS. I like > Mcomm > >> because the directory it saves everything in on the phone is > automatically > >> backed up (by another application) to dropbox right now. Then I load > that > >> image in VirtualT on the PC. > >> > > > > Ah. Well, I did write a program to sync time with NADSBox. > > > > http://bitchin100.com/wiki/index.php?title=Synchronize_Time_ > with_your_NADS > > > > -- John. > > >
Re: [M100] new project
Peter, The current clock in the M100 does just fine usually. Unless it sits for a long time. My request for another one is just me being lazy. (sort of). I use my m100 in strange ways and often I have issues where it crashes or locks up and requires a total system reset. Most of my activities with it require accurate time. I'm either logging things, tracking things or just doing notes etc. With REX it's like a dream to recover from these situations. Granted, more times than not REX is also the cause.. But right now I reset, load REXMGR, reload the RAM image and it takes seconds. Then I have to set the clock by either going into BASIC and setting the 3 variables or attaching one of my external devices and running a basic program to do it for me. Not hard mind you but when I do this same thing in VirtualT the time is always right so maybe I'm spoiled. Brian On Oct 31, 2017 7:01 PM, "Peter Vollan" wrote: Let me sure that I understand: however correctly you set the time on your Model 100, it will "drift off", because it cannot keep correct time? On 26 October 2017 at 12:58, John R. Hogerhuis wrote: > > > On Thu, Oct 26, 2017 at 12:22 PM, Brian Brindle wrote: >> >> Hey John, >> >> To move RAM images around I"m using REX, creating a backup of the RAM >> image and saving it to "disk" or in this case Mcomm or my NADS. I like Mcomm >> because the directory it saves everything in on the phone is automatically >> backed up (by another application) to dropbox right now. Then I load that >> image in VirtualT on the PC. >> > > Ah. Well, I did write a program to sync time with NADSBox. > > http://bitchin100.com/wiki/index.php?title=Synchronize_Time_with_your_NADS > > -- John.
Re: [M100] DVI cable
On Oct 27, 2017 1:19 AM, "Mike Stein" BTW, I have a couple of copies of the single sheet addendum to the DVI instructions: "Notice to Users of Radio Shack's DISK/VIDEO INTERFACE" It lists the M100 and T200 files on the system diskette and adds the T200 Kill and Restart BASIC commands; is it on line somewhere or should I scan it? I just uploaded a copy of that, and another insert with corrections to some BASIC error codes, to archive.org https://archive.org/details/TRS80DVICorrectionBASICErrorCodes https://archive.org/details/DVI263806Notice That catalog number 26-3806 matches what's on the version of the system disk that says 100/200 on it. These are crap phone app scans though. My flatbed scanner decided not to work today. -- bkw
Re: [M100] DVI cable
... and finally I have booted! I had a 2nd dvi come in, and I just booted it using the disks I already had. So now I have finally actually proven the cable parts, assembly directions, and pictures I put on tandy.wiki I went from famine to feast. I actually have *3* working original system disks now. The 2nd dvi came with a manual, and there was a system disk in a pocket in the back of that too. So next thing is to make some copies of those. Thanks for all the help along the way. -- bkw On Oct 31, 2017 9:19 PM, "Brian White" wrote: > Thanks Mike. > > I have a Teac FD-55B-01-U on the way, which should be 360k. > > I also found another disk in the packing materials for my dvi. It doesn't > boot either but it looks like it is also a system disk, even though the two > disks look different and have different catalog numbers. > > https://photos.app.goo.gl/iyQgkHnuj55Is23t2 > > -- > bkw > > > On Oct 28, 2017 8:48 PM, "Mike Stein" wrote: > > At a fast glance through the sparse documentation available it doesn't > look like any of those drives will do. > > Again, there's some confusing terminology here; I don't think Epson's dual > density is the same thing as double density and I think they're actually > talking about track density. There are three (formatted) possibilities: > 1.2 MB 96 tracks per inch, 500kbps > 740KB 96 tracks per inch, 250kbps > 360KB 48 tracks per inch, 250kbps. > > 740KB (sometimes called quad density) was not very common and Epson > probably means that their drive is only capable of two densities, 1.2MB HD > and 360KB DD as used in PCs and clones. > > The DVI disks are single-sided double density, with the same capacity as a > single-sided DD PC diskette but arranged as 40 tracks of 18 256 byte > sectors instead of 40 tracks of 9 512 byte sectors. The number and size of > sectors is a function of the controller, so the DVI drive is the same as > one side of a standard 360K DD drive as used in PCs and elsewhere. > > To read a DD diskette in an HD drive you need to slow it down from 360 RPM > to 300 RPM (or adjust the transfer rate) and you have to take two 80 TPI > steps for every 40 TPI step. It looks like an 'I' jumper on the Teac 505 > should make 300RPM available, and pin 2 would then enable it; unfortunately > there's no indication that it (or any of these drives) are capable of > double-stepping, leaving that up to the controller. > > But I could be wrong... > > m > > - Original Message - > > *From:* Brian White > *To:* m...@bitchin100.com > *Sent:* Saturday, October 28, 2017 4:09 PM > *Subject:* Re: [M100] DVI cable > > > On Oct 28, 2017 1:00 PM, "MikeS" wrote: > > What's the make/model of the HD drive? Might be trivial to configure it to > read a DD diskette. > > > Epson SD-680L > Epson SD-600 combo > Teac FD-505 combo > And on the way in, Epson SD-521 > > The SD-680L looks nice and configurable, although this pdf suggests it's > not fully configurable, but maybe that just means it can't do *single* > density? > http://jope.fi/drives/40200A03.pdf > > Easy enough to try, so I will do that next. > > > Do you only have one system disk? > > > Yeah just the one. Looks original. Factory label that says Model 100 Disk > Operating System. Obviously I intended to make copies and only use the > copies, if it worked at least once. Maybe it still will work in a different > drive. > > Or I might possibly be able to use those disk images that Steven put up on > club100 to make a new disk from scratch. > > One of my old servers might possibly have a floppy controller that would > work. That would be a whole project of it's own, since everything probably > has bad caps. Otherwise I'm hoping one of you gents would be willing to let > me mail you a few blank disks and you run the backup util to make a couple > copies? > > -- > bkw > > >
