+mizapf Posted September 26 Share Posted September 26 No, I did not move, Vilnius was just the last part of my Baltic round tour. I'm safely back, allow for a short time for me to sort things. Quote Link to comment Share on other sites More sharing options...
+mizapf Posted September 26 Share Posted September 26 18 hours ago, Brufnus said: I tried that one; couldn't initially figure out what was going on, but then I took a look at the source code and found that the error code tells me it can't find a SCSI card (one long and two short beeps). "-.." means "SYSTEM-SYS file not found". If the card were not found, it would be "-." Quote Link to comment Share on other sites More sharing options...
Brufnus Posted September 26 Share Posted September 26 2 hours ago, RickyDean said: One of my Geneve's has a 27C128 on it, so you should be fine. I'd save the existing rom information for that MFM card in case you ever wanted to put it back into operation. Yes, I did and burned the 2.0 Geneve ROM afterwards; went fine but I haven't yet tested it on the Geneve. They're not "C" eproms, but should be pin compatible with the 27C128's though, so I highly doubt it won't work. c",) Quote Link to comment Share on other sites More sharing options...
Brufnus Posted September 26 Share Posted September 26 (edited) 1 hour ago, mizapf said: "-.." means "SYSTEM-SYS file not found". If the card were not found, it would be "-." Ah! Then I've read the text in the source code wrongly. That's comforting though; that's definitely easier solved than having a hardware issue. It should be named and placed correctly however, so I'll have to dig into that. In any case, thanks! Okay, I hope you had a pleasant trip then. I like the Baltic countries very much! Edited September 26 by Brufnus Quote Link to comment Share on other sites More sharing options...
Brufnus Posted September 27 Share Posted September 27 It's unable to find SYSTEM-SYS it seems, no matter what I do... alas 🤔 Quote Link to comment Share on other sites More sharing options...
+9640News Posted September 27 Share Posted September 27 Do you also have LOAD-SYS at the root level with the 2.00 eprom? What version of the load-Sys file is it displaying? Quote Link to comment Share on other sites More sharing options...
Brufnus Posted September 27 Share Posted September 27 39 minutes ago, 9640News said: Do you also have LOAD-SYS at the root level with the 2.00 eprom? What version of the load-Sys file is it displaying? I'm not using the 2.00 eprom yet; I'm trying to boot off Michaels floppy solution. Right now I'm in the process of formatting a fresh disk and then I'll try placing SYSTEM-SYS as the first file, in case it has something to do with the physical allocation or something. However, I'll burn and replace the boot ROM later. c",) I'll use the opportunity to make a shunt from the battery to the clock chip at the same time, since it doesn't remember the time. Quote Link to comment Share on other sites More sharing options...
+mizapf Posted September 27 Share Posted September 27 @Brufnus The boot file preparation is somewhat tricky across the different BIOS versions. I had to set up different cases for combinations of floppy controller, hard disk type, BIOS, and OS version when I added the "Install GeneveOS" feature in TIImageTool 3. Give me a short overview: - BIOS version (EPROM) - Floppy controller - HD controller - GeneveOS version Quote Link to comment Share on other sites More sharing options...
Brufnus Posted September 27 Share Posted September 27 Okay, the EPROM is V0.98, I have a HFDC with a 5 1/4" drive as A: and a 3.5" drive as B:, David's MFM emulator, Horizon 512K Memex, GeneveOS 7.45. Quote Link to comment Share on other sites More sharing options...
Brufnus Posted September 27 Share Posted September 27 54 minutes ago, mizapf said: @Brufnus The boot file preparation is somewhat tricky across the different BIOS versions. I had to set up different cases for combinations of floppy controller, hard disk type, BIOS, and OS version when I added the "Install GeneveOS" feature in TIImageTool 3. Give me a short overview: - BIOS version (EPROM) - Floppy controller - HD controller - GeneveOS version Perhaps I should just go ahead and swap the EPROM with a 2.0; it was just for the fun of it and I like experimenting with all kinds of stuff. Quote Link to comment Share on other sites More sharing options...
+mizapf Posted September 27 Share Posted September 27 OK, if you hooked up the floppy drive to the HFDC, you must put LOAD/SYS on the floppy drive (HFDC requires LOAD/SYS even from floppies), and add my custom bootloader as SYSTEM/SYS. On the SCSI drive, put the real SYSTEM-SYS in the root directory. Quote Link to comment Share on other sites More sharing options...
Brufnus Posted September 27 Share Posted September 27 46 minutes ago, mizapf said: OK, if you hooked up the floppy drive to the HFDC, you must put LOAD/SYS on the floppy drive (HFDC requires LOAD/SYS even from floppies), and add my custom bootloader as SYSTEM/SYS. On the SCSI drive, put the real SYSTEM-SYS in the root directory. Yes, I did that too... LOAD/SYS is on my floppy as well. Hmmm strange that it won't boot then... 🤥 Quote Link to comment Share on other sites More sharing options...
+mizapf Posted September 27 Share Posted September 27 Ah, my bad, you said you got the beep tones - that means it already found LOAD/SYS and my bootloader. Did you try the exact configuration in MAME already? Quote Link to comment Share on other sites More sharing options...
Brufnus Posted September 27 Share Posted September 27 (edited) 33 minutes ago, mizapf said: Ah, my bad, you said you got the beep tones - that means it already found LOAD/SYS and my bootloader. Did you try the exact configuration in MAME already? I'm using a real Geneve, not emulation. Yes it does load the bootloader and also seems to recognize both the SCSI controller and the HDD (they do flash their LED's anyway), SYSTEM-SYS is in the root of that drive, so I guess there's little more I can do. It's not a big deal of course, but it'd be fun to make it work. c",) In any case, thanks for your help! Another thing I came to think of, completely different topic though... if using the SCSI drive as standalone, I guess it also means goodbye to the DSK1 emulation like the HFDC is capable of. But it should theoretically be possible to implement with the SCSI cards as well, right? EPROM code or something... Edited September 27 by Brufnus Quote Link to comment Share on other sites More sharing options...
+mizapf Posted September 27 Share Posted September 27 Yes, but emulating it in MAME first makes it much easier when you get back to the real system; you can experiment with different settings. I just tried to configure it as I first thought, but got an error message like "CANNOT LOCATE SYSTEM SYS FILE ON HFDC" (white text on cyan screen). Do you see that? Quote Link to comment Share on other sites More sharing options...
Brufnus Posted September 27 Share Posted September 27 Ah, okay... yes I agree. I'm not yet very familiar with the parameters though and barely made it work with an MFM and a floppy image. No, nothing happens except for the three beeps and then a couple of reboots and retries. Quote Link to comment Share on other sites More sharing options...
+mizapf Posted September 27 Share Posted September 27 What are your CRU settings (HFDC, SCSI, other cards)? You see the Swan, then do you also see the progress bar that my bootloader draws over it? The DSK1 emulation is part of the HFDC DSR. I think it should also be possible to implement it for SCSI drives in the Master DSR, but this is something for Tim or Beery. Edit: Concerning your booting problem, I actually did not design the SCSI bootloader to work in a system that hosts a HFDC (from which the system is supposed to boot normally). The problem may be that the LOAD/SYS from DSK1 just tries to load SYSTEM/SYS from the MFM harddisk. Quote Link to comment Share on other sites More sharing options...
Brufnus Posted September 27 Share Posted September 27 I just installed the 2.0 EPROM, but it only tries booting from floppy and tells it can't read from floppy. How does one select the boot device with this version? Quote Link to comment Share on other sites More sharing options...
Brufnus Posted September 27 Share Posted September 27 18 minutes ago, mizapf said: What are your CRU settings (HFDC, SCSI, other cards)? You see the Swan, then do you also see the progress bar that my bootloader draws over it? The DSK1 emulation is part of the HFDC DSR. I think it should also be possible to implement it for SCSI drives in the Master DSR, but this is something for Tim or Beery. Edit: Concerning your booting problem, I actually did not design the SCSI bootloader to work in a system that hosts a HFDC (from which the system is supposed to boot normally). The problem may be that the LOAD/SYS from DSK1 just tries to load SYSTEM/SYS from the MFM harddisk. My HFDC is at >1100, SCSI card at >1200, no other cards than these except for the Geneve and the Memex. No, there's no progress bar either. Yes I also considered that the HFDC may somehow interfere with it. It does flash the SCSI LED though, but it could be the reason. I can't pull it though; then I have no floppy controller, haha Quote Link to comment Share on other sites More sharing options...
Gary from OPA Posted September 27 Share Posted September 27 (edited) 39 minutes ago, Brufnus said: My HFDC is at >1100, SCSI card at >1200, no other cards than these except for the Geneve and the Memex. No, there's no progress bar either. Yes I also considered that the HFDC may somehow interfere with it. It does flash the SCSI LED though, but it could be the reason. I can't pull it though; then I have no floppy controller, haha Is the jumpers set on the SCSI for Geneve operation. Do you have a genmod? Try removing the memex card. Did you test the SCSI on a 4a to make sure it's all formatted and setup right. Can you boot up your system fine with everything on a floppy and then check the SCSI via mdos to make sure it's seeing the files. Do you have a mfm hard drive connected, and if not the mod to disable looking for a HDD because of you don't it will sit for over a minute before it times out. Edited September 27 by Gary from OPA Quote Link to comment Share on other sites More sharing options...
Brufnus Posted September 27 Share Posted September 27 2 hours ago, Gary from OPA said: Is the jumpers set on the SCSI for Geneve operation. Do you have a genmod? Try removing the memex card. Did you test the SCSI on a 4a to make sure it's all formatted and setup right. Can you boot up your system fine with everything on a floppy and then check the SCSI via mdos to make sure it's seeing the files. Do you have a mfm hard drive connected, and if not the mod to disable looking for a HDD because of you don't it will sit for over a minute before it times out. It's jumpered for Geneve, I don't have the genmod no. The card works fine from within MDOS; I've formatted and populated it, and listing and executing files from the disk works fine. It's just that it cannot find SYSTEM-SYS when I attempt to load with Michael's bootloader. Yes and no; I have David Gesswein's MFM emulator attached, but they seem to coexist fine otherwise. Indeed the timeout is kind of annoying; I just thought it would be a fun exercise and a nice option to be able to boot like that. Eventually the card will be relocated to another Geneve, by the way, once I'm done working on some archives on the one in question. Quote Link to comment Share on other sites More sharing options...
+InsaneMultitasker Posted September 27 Share Posted September 27 If Michael’s boot loader does not differentiate between the SCSI and HFDC cards, the HFDC is most likely intercepting the low level request. Why? The two cards use the same low level subroutine numbers. One possible way to test this would be to use a standard floppy controller in place of the HFDC. Another would be to move the SCSI to cru 1000. Quote Link to comment Share on other sites More sharing options...
+InsaneMultitasker Posted September 27 Share Posted September 27 Also, be sure to use the correctly named files and locations: there is mention of both SYSTEM-SYS and SYSTEM/SYS in this thread. Quote Link to comment Share on other sites More sharing options...
Brufnus Posted September 27 Share Posted September 27 20 minutes ago, InsaneMultitasker said: If Michael’s boot loader does not differentiate between the SCSI and HFDC cards, the HFDC is most likely intercepting the low level request. Why? The two cards use the same low level subroutine numbers. One possible way to test this would be to use a standard floppy controller in place of the HFDC. Another would be to move the SCSI to cru 1000. I could eventually swap the controller with the Atronic floppy only. It would be easier to set the SCSI to 1000 of course; actually I had that in mind. Right now I'm erasing the EPROM again; then I'll try and see how v1.0 behaves with these two cards as they are at the moment. Quote Link to comment Share on other sites More sharing options...
Brufnus Posted September 27 Share Posted September 27 (edited) Okay, THAT worked. After plugging it in with a 1.00 boot EPROM it showed up with the menu like on the other Geneve; it complained about missing SCSI/SYS (expected, since I hadn't copied that one in advance), so I booted from HFDC and copied LOAD-SCS in with that filename instead, and now it does indeed boot from my SCSI drive! I'm going to miss the swan, but for now I'll just keep the 1.0 ROM. Having the ability to erase and flash one's own EPROMs does indeed make life so much easier (with the Amiga's as well, for that matter). Thanks for all your patience and advices, I appreciate that and, as always, learn quite a bit new stuff along the road! Hmm I really would have loved seeing Michael's progress bar on top of my swan though, but perhaps at some other time I'll succeed with that. c",) P.S. Perhaps I should indeed experiment with having the SCSI card at >1000 later on. Edited September 27 by Brufnus 1 Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.