|
Post by hydrophilic on Nov 14, 2015 9:46:50 GMT
Thanks for your report! So besides ROM, drive 8 needs a disk with at least these files: * Config 2+ * Desktop 2+ * Input driver (mouse/joystick/pen) * Printer driver
Optional: * Pref Manager * Color Manager
That all makes sense, except the printer driver. Really strange GEOS would *require* a printer to boot. Maybe this is a limit/bug in Configure? Or the GEOS boot process in general?
Just out of curiosity, can you set your system to use 1581 as drive A? It probably would not matter (1571/1581 as drive A), but it would be cool if you could test/confirm such a setup.
Well that is just a wish (no worries if you can't do it / don't have the time)... more important is: how does GEOS ROM compare to pure disk version? Faster boot but otherwise the same? Switching apps faster? I guess Accessories are the same speed!? Is the OS more stable using ROM?
I remember in "original GEOS" (came with C64 of a friend), that there would often be "system errors". Sometimes GEOS would report the error and halt, and sometimes GEOS would just crash (no error message). GEOS 128 V2 has been more stable (far fewer "system errors"), but I was just curious (with ROM version) if the errors are less frequent and/or "more recoverable" (i.e., the entire OS doesn't crash).
Well, if you don't have a way to reliably generate a crash in the disk version, then I don't see how you could test the ROM version. Anyway, would love to hear your thoughts regarding stability of the ROM version versus disk.... thanks!!
|
|
|
Post by robertb on Nov 15, 2015 7:59:59 GMT
Is the OS more stable using ROM? I remember in "original GEOS" (came with C64 of a friend), that there would often be "system errors". If only Wheels had come in a ROM version... Wheels was far more stable than GEOS. Of course, if any changes were made to RAM, boot settings, input and printer drivers, clock source, and drives, then you'd have to burn a different ROM with the changes. Barring any Wheels ROM solution, then the best alternative would be to run Wheels from a RAMLink, which would be far more flexible than any ROM in matters of system changes and would give instantaneous access like a ROM. Truly, Robert Bernardo Fresno Commodore User Group www.dickestel.com/fcug.htm
|
|
|
Post by nonefornow on Nov 16, 2015 15:53:52 GMT
Thanks for your report! So besides ROM, drive 8 needs a disk with at least these files: * Config 2+ * Desktop 2+ * Input driver (mouse/joystick/pen) * Printer driver Optional: * Pref Manager * Color Manager That all makes sense, except the printer driver. Really strange GEOS would *require* a printer to boot. Maybe this is a limit/bug in Configure? Or the GEOS boot process in general? That's a good point. I really do not know. I was assuming that the printer driver is needed based on the instruction in the original GEOS. I have placed a printer driver in the boot diskette even though I do not have a printer attached to the computer. I'll try to see what happens if I remove the printer driver. Just out of curiosity, can you set your system to use 1581 as drive A? It probably would not matter (1571/1581 as drive A), but it would be cool if you could test/confirm such a setup. Yes and no. Because I am using a C128DCR the ROM chip was set up to use the internal 1571 as drive A. With a flat C128 one could set up the C1581 as drive A but one will need a ROM chip prepared for that. Well that is just a wish (no worries if you can't do it / don't have the time)... more important is: how does GEOS ROM compare to pure disk version? Faster boot but otherwise the same? Switching apps faster? I guess Accessories are the same speed!? Is the OS more stable using ROM? I remember in "original GEOS" (came with C64 of a friend), that there would often be "system errors". Sometimes GEOS would report the error and halt, and sometimes GEOS would just crash (no error message). GEOS 128 V2 has been more stable (far fewer "system errors"), but I was just curious (with ROM version) if the errors are less frequent and/or "more recoverable" (i.e., the entire OS doesn't crash). Well, if you don't have a way to reliably generate a crash in the disk version, then I don't see how you could test the ROM version. Anyway, would love to hear your thoughts regarding stability of the ROM version versus disk.... thanks!! It is my understanding that most of the system errors of the original GEOS were in fact as a result of the copy protection. GEOS 2.0 is coded without such protection. I have not experienced any crashes so far. With the ROM chip it appears to load faster that the disk version, although I am not able to have it remember all the CONFIG settings.
|
|
|
Post by nonefornow on Nov 16, 2015 15:57:44 GMT
Of course, if any changes were made to RAM, boot settings, input and printer drivers, clock source, and drives, then you'd have to burn a different ROM with the changes. This is also another good point. I did not fully understand all the ramification of each personal set up. But apparently it is possible to burn different ROM chips with different set ups. I'll have to investigate more.
|
|
|
Post by ilkerficicilar on Feb 16, 2016 14:25:43 GMT
Hello,
Can you please measure the load time with this GEOS ROM chip?
For example, in my C128D setup (no GEOS-ROM) it takes 55 seconds (the time between power-up and the moment that the pointer becomes visible).
But, my C64+SD2IEC+FCIII+ setup loads GEOS in less then 17 seconds.
So, I wonder what is the load time with this ROM?
Thanks in advance.
|
|
|
Post by nonefornow on Mar 1, 2016 15:07:19 GMT
From the moment I turn the switch on to the moment the pointer is visible and available I clocked 30.58 seconds, in 80c.
Next I'll try to remove the ROM and load straight from disk. Let's see what happens.
|
|
|
Post by Ratteler on Apr 5, 2016 15:53:59 GMT
Could the chip be set up to load from a UIEC device? I would love to get a GEOS chip in my 128's, but doubt I'll ever use a real floppy ever again.
|
|
|
Post by ilkerficicilar on Apr 18, 2016 21:18:35 GMT
After the addition of this ROM a week ago, I connected a DS3231 RTC and the respective rtcgeosload to the setup as well. And, a SD2IEC acts as the 2nd drive, with an autoswap.lst file. The main disk in the interval drive contains standard PIM accessories (Y2K fixed)...
But I'm not satisfied with the speed. It boots in ~47 seconds, despite the ROM. Now I'm trying to set interleave properly, otherwise I had to change internal drive to 9 and SD2IEC to 8...
As a plan B, I can burn another eprom that exchanges drive numbers by issuing "u0>[10]" "u0>[8]" "u0>[9]" to the respective drives prior to boot.
|
|
|
Post by nonefornow on Jun 22, 2016 23:36:17 GMT
Could the chip be set up to load from a UIEC device? I would love to get a GEOS chip in my 128's, but doubt I'll ever use a real floppy ever again. The chip could have been programmed to load from a 1541, a 1571, or a 1581. So my guess is that it could be set up to load from the UIEC device.
|
|
cdawe
Windows User
Posts: 14
|
Post by cdawe on Feb 25, 2017 15:56:25 GMT
Hi guys,
I've got a 128DCR too, and I was wondering how much of a pain it is to get something like this to work. I don't have GEOS 128 though...
Curt
|
|