|
Post by nonefornow on Nov 7, 2014 1:01:44 GMT
Enter "RBOOT". RBOOT in GEOS loaded itself into the memory of the REU and allowed to rebott without losing anything stored in the REU. That's were the "shell OS" could reside while waiting for commands, since most programs to not make use of the REU.
I concurr that the OS should make services available, add functionality, but not necessarily recreate the existing services. I.E. in addition the the OS GEOS also added a wordprocessor, a spreadsheet a few other apps. That in a form or another existed running from BASIC or ML.
|
|
|
Post by nonefornow on Nov 5, 2014 20:53:42 GMT
Here's my thoughts. In no particular order. I really do not know of any other OS for the C128 in addition to the one you mentioned. And I have not use any other except for GEOS. But if we are discussiong, on a theoretical level, the options, features, and functionality of a new OS for the C128, I think, we should keep in mind the old DOSShell, just for reference. It is both a GUI and not. It allows for text modes and graphic modes. It sits on top of an OS (DOS) but also adds functionality for the users that do not want to always have to type commands, altought it has its own sort of CLI. It runs all the programs that can run under the OS.
In that sense GEOS had to produce not only the OS but also all the programs such as spreadsheets, wordprocessors, games etc. A DOSSHELL like OS would could sit on top of basic while running all existing programs. Use of the RAM is almost a necessity and with the Shell in RAM will not interfere with the software. Unless such software makes use of the RAM. Of that I am not sure.
In reference to the issue of "user's programming" to the extent that the user's programs run in Basic or ML the OS will support, and it does not forces the user to learn a new programming language.
Back in the days of DOS 6.22 I liked DOSSHELL better than Windows (3.1?)
|
|
|
Post by nonefornow on Oct 8, 2014 14:41:04 GMT
I had the idea (crazy, I know) to remove the disk drive out of my C128D to try to clean underneath. But now I am not sure how to plug back in the wires that go to the disk head. The two wires end into the black plug - but which direction do it fit into the mother board? Which one is pin 1 on the MB and where is pin 1 on the plug? See the attachment. But I will take more picture to illustrate. Thank you.
|
|
|
Post by nonefornow on Oct 3, 2014 17:55:24 GMT
Doncha love modern technology? It's a necessary evil. But I still prefer vintage computers. When the machines had personality and each had different shapes, forms, and characteristics. Otherwise I would not be hanging around in a retro-forum.
|
|
|
Post by nonefornow on Oct 2, 2014 15:14:45 GMT
Reset and CFG are in PDF format. It sounds as if you may have an issue with the Adobe add-in of Win8. I also find it easy to just download the magazines and read them off line.
|
|
|
Post by nonefornow on Oct 1, 2014 14:33:40 GMT
|
|
|
Post by nonefornow on Sept 28, 2014 22:40:03 GMT
|
|
|
Post by nonefornow on Sept 26, 2014 16:48:15 GMT
Hi Miro,
Sorry but I do not have a C1750 to trade.
I was just trying to understand the reasons as to why C= would limit the C128 expansion to 512K when in reality it looks as if the C128 can handle more RAM.
|
|
|
Post by nonefornow on Sept 26, 2014 16:43:06 GMT
I tested the Wheelssc12844S1.D64 on winvice without emulating an REU and I get a message that Wheels requires ram expansion. I was going to post a screenshot but I do not know how.
I re-run with winvice emulating a 512K reu. And everything went just fine.
|
|
|
Post by nonefornow on Sept 25, 2014 14:53:31 GMT
That's what the C=128 box says.
Since there were only two REU made by Commodore for C128 - 1700 with 128K and 1750 with 512.
Does it mean that no-one contemplated to have other REU with more memory?
Or that really the C=128 can only handle 512K extra?
|
|