Now that is cool. Thank you! On Feb 27, 2018 9:38 AM, "Ken Pettit" <[email protected]> wrote:
> Hey Guys, > > Back in 2011 I started a disassembly of the dvidos / diskbasic (wow, was > that really 7 years ago?). Took me quite a while to figure out where I had > saved it actually. I didn't get it any where near complete like TS-DOS, > but I have attached it here for reference in case anyone is interested. > > Ken > > On 2/27/18 4:06 AM, Brian White wrote: > > Here you go. It worked. Except note all the caveats at the top of the text > file. > > https://drive.google.com/open?id=0Bys6eLbSbYyhOW5UOWhlcTRiQXc > > But it worked. I did a hard reset on a 102, and restored the tback image > that had dvidos and diskbasic installed, preventing any possibility of the > DVI itself re-installing them, and the dvi commands in basic worked. > > So you can restore this image onto some other 102 (possibly also a 100) > and what you have is the same as if you had a dvi and it installed dos and > disk basic the normal way. > > The caveats being this is a full ram image of my 102, not a nice portable > system-agnostic installer or program. My 102 happens to > * be a 102, not a 100 > * be running a main system rom from the REX wiki page with REX and Y2K > modifications > * have 32K installed > > You probably can only restore this onto another machine with 32k installed. > You might possibly only be able to install this on a 102 and noyt a 100. > 100 and 102 are so similar in hardware that it's possible to run a 102 rom > on a 100 hardware, but that doesn't guarantee that a ram image from a > running 102 would actually run without any errors on a 100 main rom. > The rex and y2k hacks probably have no adverse effects, but who knows, > it's a difference from a stock machine and so it could possibly matter, or > at least, you have to be told about it. > > All my 100's are running that same 102 rom, so I can't make a model 100 > image right now. Even if I used one of my 100's , the ram image would just > be the same as this 102 image, and might not work on anyone else's 100. > > I do have the means to put a stock rom back in a 100, and I do have the > means to do this on a 200, so I may do those too sooner or later. > > -- > bkw > > > On Mon, Feb 26, 2018 at 6:37 PM, Brian White <[email protected]> wrote: > >> I could do that sure. It's an interesting question. Should be perfectly >> possible to "install" the dvi dos by some other means than having the dvi >> do it, but I don't know if anyone has done it. But even without that, a >> full ram dump seems like it should be at least one sort of brute-force way >> to do it if nothing else. >> >> But it seems like the stuff Steven Adolph picked apert here >> >> http://www.club100.org/memfiles/index.php?&direction=0&; >> order=&directory=Steve%20Adolph/DVI%20boot%20disk%20files >> >> should form a pretty good start on an installer, since he even has the >> IPLs not just the dos and basic. >> Actually, since I have a working setup the "normal" way, I'm in a >> position to try playing with those files and see if I can get them to >> install, dump the ram, and see if the result is the same as a dump of a >> normal install. >> >> Then again, maybe even having the IPL doesn't help that much here, >> because surely the IPL works from the assumption that the DVI is hooked up >> with the system disk loaded, and fetches things from it. We need an ipl >> that gets the stuff from a local file or from it's own self. If you had a >> replicate dvi that could deliver the stuff the way the ipl expects, then it >> could also inject the ipl the normal way in the first place. >> >> I'll try to make a full ram image tonight, along with some sort of >> directions how to restore it onto a m100. >> I've never used any full ram image backup/restore utilities other than >> what's built-in to REX and the bank-switching feature of QUAD and PG Design >> ram upgrade hardware. But I assume there is something. I guess TBACK is >> that? >> >> -- >> bkw >> >> >> On Mon, Feb 26, 2018 at 5:31 PM, Mike Stein <[email protected]> wrote: >> >>> I don't see anything wrong with using modern intelligent peripherals; I >>> used a dedicated MS-DOS laptop to put the M100's display on an LCD TV over >>> the serial port. >>> >>> I guess the simplest would be for someone with a DVI to configure the >>> M100 and then dump RAM using TBACK or similar; you could then load that >>> configuration into your M100. >>> >>> Maybe Brian can do that since it sounds like his DVI is readily >>> available; if not I could do it but not for a while. >>> >>> m >>> >>> ----- Original Message ----- >>> From: "VANDEN BOSSCHE JAN" <[email protected]> >>> To: <[email protected]> >>> Sent: Monday, February 26, 2018 5:13 PM >>> Subject: [M100] DVI duplication >>> >>> >>> > Hello, >>> > >>> > Despite that some disagree about using a periferal device, more >>> intelligent than the Model T itself, I do want to continue to see if I can >>> use a Raspberry Pi to act as such. >>> > >>> > In order to be able to investigate the possibility of the duplication >>> of the DVI video-out function via a Raspberry Pi, I'd need a way to load >>> the drivers to a Model T. So far, and AFAIK, there's only one way to do >>> that: with a DVI. I don't have one. Is there a way to emulate this, or >>> another way to inject the drivers in the Model T ? >>> > >>> > Mij jaag >>> > je niet zo >>> > gemakkelijk weg. >>> > Jan-80 >>> > VIVAQUA et HYDROBRU ont fusionné. >>> > VIVAQUA est votre société d'eau en Région de Bruxelles-Capitale. >>> > >>> > VIVAQUA en HYDROBRU zijn gefusioneerd. >>> > VIVAQUA is uw waterbedrijf in het Brusselse Hoofdstedelijk Gewest. >>> > >>> > [http://www.vivaqua.be/facebook.png] Rejoignez-nous sur Facebook - >>> Volg ons op Facebook >>> > >>> > DISCLAIMER >>> > Pensez à l'environnement, n'imprimez cette page et ses annexes que si >>> c'est nécessaire. Ce message électronique, y compris ses annexes, est >>> confidentiel et réservé à l’attention de son destinataire. Si vous n'êtes >>> pas le destinataire de ce message, merci de le détruire et d’en informer >>> l’expéditeur. Toute divulgation, copie ou utilisation de ce mail est dans >>> ce cas interdite. La sécurité et l'exactitude des transmissions de messages >>> électroniques ne peuvent être garanties. >>> > Denk aan het milieu; druk deze pagina en de bijlagen alleen af als het >>> nodig is. Dit e-mailbericht (inclusief zijn bijlagen) is vertrouwelijk en >>> is uitsluitend bestemd voor de geadresseerde. Als dit bericht niet voor u >>> bestemd is, wordt u verzocht het te wissen en de afzender te informeren. >>> Het is in dat geval niet toegestaan dit bericht te verspreiden, te kopiëren >>> of te gebruiken. We kunnen niet garanderen dat de gegevensoverdracht via >>> het internet veilig en nauwkeurig is. >>> > >>> >> >> >> >> -- >> bkw >> > > > > -- > bkw > > >
