Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: Michele31415 on January 20, 2012, 10:19:45 PM
-
The Deneb is a very cool card that gives my Amiga access to USB, but the splash screen it puts up on boot is driving me nuts. First, two little lines laboriously trace out the word "DENEB" on the screen. Then it gets filled in with some pattern. Then the pattern falls to the ground and DENEB remains so you can admire it. Then it disappears. Then the whole $%&# thing starts over again. Not until that's all over with does the machine continue booting - and it takes at least a minute.
The first time I saw this, it was cute. The second time it was boring. But now it's simply beyond irritating. Is there any way to make this piece of animation simply go away?
-
Works on persnickety electronics as well!
(http://forums.prosoundweb.com/index.php?action=dlattach;topic=135065.0;attach=3879;image)
not that anyone should ever mute a deneb!
-
Do you have Luciferin? It's the tool for managing the FlashROM on the Deneb. Just fire that up and move the intro to your hard drive and out of the Flash. See http://platon42.de
-
Having it means that you probably have the default installation modules inside your Deneb.
These are the Deneb devices, poseidon.library, mass storage device, and some other classes along with the INTRO module as Matt_H said.
Just fire up Luciferin, copy the flash contents to a folder for backup purposes and save/flash either your modules of choice or even an empty flash (if you don't want any extra module inside) and you're gonna be set :)
Intro is cool but only for a couple of times I guess :P
-
Just fire up Luciferin, copy the flash contents to a folder for backup purposes and save/flash either your modules of choice or even an empty flash (if you don't want any extra module inside) and you're gonna be set :)
OK, I got Luciferin running and there's a whole list of items on the left side and another list of items on the right side. And there's a message on the bottom that says "Loading modules list from 'Default.mods'...failed!" (whatever that means).
In the right pane under the FlashRom tab, I see something called "DenebIntro". I assume that's what I want to get rid of. But ir's not at all clear how to do that. And after reading two paragraphs of warnings in the documentation about how this stuff is for experts only and one wrong move can brick your machine, I'd rather not experiment with this. :angry: Thanks.
-
The message isn't important so no worries :)
Ok... some clarification then.
Left side is your local hard drive. From here you can change to the path you want to either use to download files from Deneb's flash or choose files (modules) to load into Deneb's Flash
Right side is Deneb.
- First tab Local exists for you to drag & drop files (modules) from left side in order to put it into Deneb's Flash. When you're ready to flash Deneb... just press the button Upload.
- Second tab FlashRom is the Flash as it is now (you will see the contents of what exists in there). You can't do alter anything in that tab but to check what you got and download it to the Left side=Local hard drive.
- Third tab Booloader has general options about how Deneb will react upon booting. No need to change anything there.
-
Thanks for the explanation. So there's no way to remove just one thing from the FlashRom, you have to rebuild the list of everything minus the one item you don't want?
So what I need to do is Download everything I want to keep from the right side to the left side, then drag & drop them from there into the Local pane and then click Upload? Is that right? (Just want to be 100% sure)
-
Verify output size?
Is Deneb USB designed with a generic "usb.library" that calls a hardware specific "deneb.library" ?
(btw, can one boot a USB drive from Deneb?)
-
So what I need to do is Download everything I want to keep from the right side to the left side, then drag & drop them from there into the Local pane and then click Upload? Is that right? (Just want to be 100% sure)
You're absolutely correct :)
Is Deneb USB designed with a generic "usb.library" that calls a hardware specific "deneb.library" ?
(btw, can one boot a USB drive from Deneb?)
Deneb is a device, and it has 3 software devices that support it (dma, pio, zii). Apart from the poseidon.library there are the USB classes like HID, mass storage, etc.
Putting deneb device, poseidon.library, massstorage.device and your current psdstackloader configuration file, and you can boot just fine from Deneb via USB :)
It works pretty fast as well :)
I managed to boot even from Subway USB in an A600/030 but it was done only for testing/fun purposes. You can check it out here: http://www.youtube.com/watch?v=8gtDZUm46ks
-
Well, one step forward, two steps back. I put the "2632" command in my startup-sequence file as recommended in the DKB manual and now the machine won't boot anymore. It goes all the way through the "Deneb intro" thing twice and then hangs. I'll have to boot from my 3.9 emergency floppy tomorrow and take that line out. At least I hope that's why it's not booting now. Sigh...
-
Are you familiar with Early Startup Control? Hold both mouse buttons while booting and you'll get a menu with some boot options, including Boot with No Startup-Sequence. That will drop you into a basic shell, so you can run a text editor from there and comment out lines in your startup-sequence without needing to dig up a boot floppy.
I would be suprised if 2632 isn't the problem.
-
Well what I did was boot from my OS 3.9 Emergency floppy. That let me edit out the 2632 command from startup-sequnce. After that, it rebooted OK. So then I ran Luciferin and was able to reflash the Deneb card, removing the DenebIntro module (as well as that annoying "StayingAlive" requester).
Then I rebooted again. Now the machine won't boot at all. All I get is a blank screen. I finally had to pull the Deneb card out. With that gone, it boots OK. So now what? Did I just brick my Deneb?
For the record, I reflashed using the following list:
denebpiousb.device
denebz2usb.device
hid.class
hub.class
massstorage.class
poseidon.library
PsdStackloader
Heeeeellllp!
-
First of all you haven't bricked your Deneb by just using Luciferin :)
Second, you don't need to pull out Deneb if it doesn't boot. Putting the Jumper into ROM position, disables Deneb's flash so it won't interfere in the boot process.
Second, I'd suggest you to remove everything from Deneb's flash and boot your system.
Poseidon doesn't need to be in Flash except you require USB things before booting Workbench (like USB mouse, booting from USB sticks etc). If you don't need such stuff, there's no need to have Poseidon.library, classes and Deneb devices into the Flash.
So... If your system works just fine without anything... then install Poseidon, configure it and if it works, insert into Deneb's flash the correct device that works on your system, and the PsdStackLoader that resides on your Env-Archive folder. Don't forget that every change you make on the USB configuration needs a fresh PsdStackLoader!
-
There's a jumper you can set to disable the Deneb Flash ROM on boot. Try that.
-
Doh Mfilos types faster than me :D
-
So... If your system works just fine without anything... then install Poseidon, configure it and if it works, insert into Deneb's flash the correct device that works on your system, and the PsdStackLoader that resides on your Env-Archive folder. Don't forget that every change you make on the USB configuration needs a fresh PsdStackLoader!
OK, so I stuck in the "disable ROM" Deneb jumper and rebooted. This time the system came up normally (and for once without the Deneb animation and the "Still Alive" requester) but also without my 8 gig USB stick device that's plugged into the internal Deneb connector showing up in WB.
So what are you suggesting - that now I should reflash the Deneb ROM again with nothing but poseidon.library and PsdStackloader in the list? Does it matter what order they're in? For that matter, is it even possible to set the order? It seemed like when I was adding stuff last time they ended up in alphabetical order, although that's not the way they were originally.
All I really want is to be able to use USB devices on the Amiga. I'm not too concerned about being able to do USB boots.
The problem now is that when I run Luciferin, it says "I'm sorry, I couldn't find a Deneb device", So now what?
-
Do you remember old SCSI cards that had an autoboot jumper? Setting it to be disabled meant that you had to load drivers manually, in software. The ROM jumper on the Deneb works the same way. Fire up Trident, configure Poseidon, bring the stack online, and hit Save.
Now go into Luciferin. There's a menu option called quick setup that loads in the correct Poseidon modules. Try that.
I noticed earlier that you had both denebpiousb.device and denebz2.device in your modules list - that might be your problem. denebpiousb.device is only for A3000s or A4000s. Since you've got an A2000, make sure that only denebz2usb.device is configured in Poseidon/Trident and getting uploaded to the Flash.
Also, on the Bootloader tab in Luciferin, set the 3 options the following way: Re-install on every boot, left mouse button, status as colour. Now if something bad happens, just reboot while holding the left mouse button and the Flash will be disabled - just as if you'd used the ROM jumper. Extremely convenient feature!
-
Ah ha - thank you so much, Matt. Obviously my assumptions about the way this card worked were incorrect. Your explanation really helps. And I'll bet anything that you're right about the pio device too. I have no idea how that got it there. I'm pretty sure I just followed the installation instructions that came with the card.
It's getting late tonight but I'll give that a try first thing tomorrow :-)
-
" Fire up Trident, configure Poseidon, bring the stack online, and hit Save."
I hate to sound dense, but can you expand on that a bit? I got the "fire up Trident" part OK, but how do I bring the stack online? In Trident I see menus for controllers, devices and classes (oh my) but I need some help in finding my way to Oz, as it were. Thanks.
-
" Fire up Trident, configure Poseidon, bring the stack online, and hit Save."
I hate to sound dense, but can you expand on that a bit? I got the "fire up Trident" part OK, but how do I bring the stack online? In Trident I see menus for controllers, devices and classes (oh my) but I need some help in finding my way to Oz, as it were. Thanks.
There should be an "Online" button at the bottom of the window :)
-
OK, well scratch what I said last time. The machine did boot, but the reason Trident said it couldn't find a Deneb board was because I hadn't reseated it fully in the card slot after setting the "No ROM" jumper. I also realized that there were no green LED's on on the Deneb.
So I reseated the card fully and rebooted. Now the machine won't boot at all. The No Rom jumper is in place, the top two LED's on the Deneb are lit ("FPGA booted" and "Zorro II mode"), but absolutely nothing happens, no disk activity or anything. It won't even boot from DF0.
I did the L-R mouse button boot and ran the Expansion Board Diagnostic. This is what I got:
Board Number Manufacturer Product Status
1 514 81 Working
2 514 3 Working
3 4626 23 Working
4 3643 18 Working
4 3643 19 Working
5 513 1 Working
The Deneb is board no. 4, mfr. 3643. According to the Deneb manual, this should show up as Products 18 and 20. I'm seeing 18 and 19. Is this (part of) the problem?
The current configuration, looking from the front is
Slot Board
1 empty
2 A2088
3 Deneb
4 Xsurf
5 A2091
6 empty
CPU A2630 with DKB2632
If I pull the Deneb out, it boots normally. Any ideas? I'm starting to wish I had just left the fool thing alone. At least before I reflashed the ROM, it was working.
Update: After about a dozen reboot attempts, I got it to boot off the Emergency OS 3.9 floppy, with the jumper removed on the Deneb. But now when I click on Trident, I get an error "Failed to load version 3 of Poseidon.library". All I can do then is click "Cancel". What's that all about?
Update 2: OK, I figured out how to assign the libs: so Trident was happy. Now in Trident I click to the Controllers panel and see Unit = 0, Online = No, and Product = unknown until online. So I click on the "Online" button at the bottom of the window and I get an error:
"Failure poseidon.library Opening DEVS:USBHardware unit 0 failed deviceInit failed to open(-1)".
This message is repeated three times. Now what?
Update 3: Just for laughs, I tried running Luciferin again. This time I get a pop-up error
"Your Deneb card has the ROM-OFF jumper set and thus the Flashrom contents are currently "DEACTIVATED" until you remove the jumper. This is only an information."
But I removed the jumper one or two reboots ago! This is shall we say, slightly mystifying.
-
Have you tried inserting Deneb in another zorro slot (for example the first empty one you got)?
Also, what version of Poseidon are you installing? Version 3 of Poseidon in your message is old stuff. You should get the newer version from Chris Hodges website here: http://www.platon42.de/index2.html
-
"Have you tried inserting Deneb in another zorro slot (for example the first empty one you got)?"
No I haven't. I only have one empty one all the way to the right, but I can't use it because the 2632 blocks it. I could try pulling the 2088 and moving the Deneb one slot to the left.
"Also, what version of Poseidon are you installing?"
Yup - 3.0. That's what came with the Deneb. Thanks for the link. I grabbed the latest Poseidon and Trident and will install them tonight.
-
Um, I have a stupid question - if the only way I can get the machine to boot is by inserting the Deneb "no rom" jumper, but Luciferin refuses to rewrite the rom when that jumper is in place, then how the heck can I ever change the contents of the rom?
-
Get Poseidon 4.4 installed first and report back.
Did you try the "hold left mouse button to disable Flash" trick I mentioned earlier? The board ships with the settings I described, so unless a previous owner changed them, you should be able to disable the Flash in software.
Your Deneb may need a firmware update (http://www.e3b.de/usb/main_updates_e.html) as well, but let's not introduce that variable just yet.
-
This is a strange default feature. Does everyone who doesn't want to be annoyed all the time have to go through this whole Luciferin mess?
-
This is no mess at all. Luciferin is easy stuff, it just needs a bit of attention.
Btw I dont' recall Deneb coming with Poseidon 3.x
I got one of the first Denebs in first run and it came with Poseidon 4.0 burned into it's unwritable flash memory so you could install it easily with it! No floppy disks required to get it up and running!
When you get Deneb the jumper is set to RES position in which the Unwritable flash is enabled so you can install Poseidon. After you install you power off Amiga, and put the jumper in SPR position.
It's all written in the manual.
-
"Luciferin is easy stuff, it just needs a bit of attention."
Sure - it's easy once you know how it works.
"Btw I dont' recall Deneb coming with Poseidon 3.x"
Well mine did. I bought it brand new from Amikit on 8/6/08 and followed the installation directions exactly. I never downloaded any Deneb software from anywhere else, so that's the only place 3.0 could have been.
-
Get Poseidon 4.4 installed first and report back.
Did you try the "hold left mouse button to disable Flash" trick I mentioned earlier? The board ships with the settings I described, so unless a previous owner changed them, you should be able to disable the Flash in software
Poseidon 4.4 downloaded and installed without problems. I also installed the new version of Luciferin - again it installed OK.
Thanks for reminding me about the left-button boot. I just missed that somehow. I tried that and hey presto, it booted normally from the hard drive with the Deneb installed with no jumpers on it.
So I fired up Trident and clicked on "Controllers". This time I saw this:
USB Hardware Contollers available
Name Unit Online Product
denebz2usb.device 0 Yes Deneb EHCI USB Host Controller
denebpiousb.device 0 No unknown until online
So that's different! Last time, this pane was empty. So we're clearly making some major progress. Can you tell me exactly what I need to do now to get the pio device (which is apprently screwing things up) out of the ROM? I'm so paranoid about this now I don't want to screw it up. Thanks.
-
Just select the denebpiousb.device and click delete to remove it permanently.
Just leave the denebz2usb.device and hit online. If it turns up Green then you're ok and you only need to press SAVE and reboot :)
-
And that deletes it from the Flash rom too? I thought I had to use Luciferin to do that.
By the way, even without clicking on anything in Trident yet, I noticed that my USB stick is now showing up on the WB screen, and when I open it, my files are all there.
-
No it doesn't delete it. Poseidon doesn't have to do anything with the Flash.
I just told you to delete one of the 2 entries in Poseidon's configudation.
You ought to have only one entry per device. Alas since you only have one Deneb and it operates in Z2 mode, you only need the Z2 Deneb device and delete any other.
Seeing your USB stick under WB is a good sign :)
Also check what you have in your Flash via Luciferin. My advice would be to save a Flash with nothing on for starters to be sure you don't need to press Left Mouse Button on boot to disable what exists in there every time.
Empty it all, and if everything works fine, start filling the Flash with any module you feel best :)
-
OK, I think I've got it now. I deleted the pio device using Trident and then saved that. Then I used Luciferin to reflash the rom with nothing in it. Then I I did a normal reboot (no mouse buttons presses, and no jumpers on Deneb). Surprise - everything came right up, including the icon for the USB stick! I guess I thought all that poseidon stuff was required to be in the flash rom in order for the Deneb to work but apparently that isn't the case.
So I guess the only remaining question is, if I'm not planning to boot from a USB device, do I really need to store anything in the flash rom at all?
Anyway, thanks very much to you and Matt for helping me figure out this Chinese puzzle.
-
So I guess the only remaining question is, if I'm not planning to boot from a USB device, do I really need to store anything in the flash rom at all?
Short answer: No.
The only thing I actually have on my ROM are the two modules to stop my floppy clicking and to disable the IDE port on the A4000 motherboard to speed up booting (I have a FastATA4000).
-
Hooray! You should do a cold restart to make sure everything still works with an empty Flash.
A bit more on how this all works: Your Poseidon configuration is saved in a combined config file/executable. Can't recall the name off the top of my head, but running that file will bring the stack online, and I believe the Poseidon installer adds it to user-startup by default. So that might be why your USB stick shows up on a no-Flash boot. As Darrin says, you can run without the Flash completely if you prefer.
Because your settings are in that one file, if you change the configuration you need to re-upload the Flash to make sure the USB drivers are receiving the right settings from a cold start.
So it sounds like you've got a good, safe config file. Now you should be able to run Quick Setup from the Luciferin menu to have everything important automatically set to get uploaded to Flash.
One question, though, have you had your USB stick plugged in this whole time? With Poseidon's default settings, my machine would hang with a USB stick inserted on boot. Something to do with timeout settings. Changed those, re-uploaded the Flash, and now everything works. I wonder if you were running into something similar?
-
As Darrin said... No :)
Deneb's flash is an awesome feature that works awesomely well and easy. Just use what it feels best for you. Stuffing it with things you don't know it's not good.
The fact that you have your USB showing upon boot is because of User-Startup's "PsdStackLoader" running upon boot :)
That initializes the stack based on your saved configuration alas all is working.
I'm glad you sort it out in the end. It's not so difficult, it's just need some understanding on how the device works and you're set.
Cheers
P.S. Matt_H got me this time :)
-
P.S. Matt_H got me this time :)
But PsdStackLoader is the name of the file I couldn't remember. It's a team effort :)
-
One question, though, have you had your USB stick plugged in this whole time? With Poseidon's default settings, my machine would hang with a USB stick inserted on boot. Something to do with timeout settings. Changed those, re-uploaded the Flash, and now everything works. I wonder if you were running into something similar?
Yes! When I first installed the board, I saw the internal port and thought to myself, what good is that? The obvious answer is a USB thumb drive to use for backups. So that was the first thing I added and it's been there ever since.
What's odd is that I only started experiencing total boot failure after I tried reflashing the ROM. Another weird thing is that every time I booted the Deneb intro always played twice, right from the very beginning. Originally I assumed that was just the way it was. Now I'm thinking the machine was doing an unasked for reboot after the first time through DenebIntro.
In retrospect, three things were key in solving this problem. First was using the left button boot to get the machine to even start up at all. Second was downloading the latest Trident. And third was removing the pio device from the flash rom. I did a cold boot and everything is still good.
I was greatly confused by the presence of two different utilities, Trident and Luciferin, both purporting to influence the operation of Deneb. And with no real documentaiton about what they do or how to use them, I was pretty much lost. So many thanks again to everyone who helped me bring this problemn to a successful conclusion. You guys are awesome.
-
Are you running 3.9? Sounds like your machine is resetting after applying SetPatch.
-
Seeing the intro two times means that you indeed you have OS3.9 (as I can see from your signature as well).
OS3.9 Reboots your machine when the SetPatch runs in Startup-Sequence (in order to load the updated modules of the file "AmigaOS ROM Update" that resides in DEVS).
Since Deneb loads by default the flash in every reboot, that's why you saw the Intro 2 times in every power on :)
You can disable the Intro Logo ofc by clicking the left mouse button but after some time... even that... gets irritating lol
I'd suggest at a point to put Kickstart 3.9 Modules inside Deneb to have a rebootless system that boost faster :)
I can help you with that if you can't make it on your own.
Cheers
-
I'd suggest at a point to put Kickstart 3.9 Modules inside Deneb to have a rebootless system that boost faster :)
I can help you with that if you can't make it on your own.
I am indeed running OS 3.9 and this sure sounds like the thing to do. My 2000 seems to take an awful long time to boot, even by 1980's standards.
Now that I've finally figured out how to use Luciferin (I think), if there's something I can put in there to eliminate the double-boot, that would be very cool indeed. What do I have to do?
-
There are command line tools (I think one is included with Luciferin) that can extract the component pieces of the Devs:AmigaOS ROM Update file. You can then load those into the Flash to accelerate a cold boot (some of them need other patches applied first - also included). I'll post the list of the contents of my own Flash when I get home so you can see what to expect.
If you're especially ambitious you can compile those pieces back into a complete Kickstart 3.9 image and load that in instead. I've found this method to be less usable, since holding the left mouse button doesn't always clear it out at boot.
-
Sounds good. I timed it and right now it takes 2 minutes and 5 seconds from the time I hit the power switch until the time all of the icons have painted on the WB and the machine is ready to use.
-
Ok, I have the following in my FlashROM:
romupdate.idtag
exec.library
denebpiousb.device
massstorage.class
serialcp210x.class
asixeth.class
pegasus.class
stir4200.class
palmpda.class
bluetooth.class
serialpl2303.class
printer.class
cdcacm.class
dm9601eth.class
ethwrap.class
rawwrap.class
moschipeth.class
poseidon.library
rtl8150eth.class
hub.class
input.device
hid.class
egalaxtouch.class
camdusbmidi.class
simplemidi.class
dfu.class
bootmouse.class
bootkeyboard.class
PsdStackLoader
NCR scsi.device
scsi.device
console.device
ptp.class
bootmenu
FastFileSystem
usbaudio.class
usbvideo.class
shell
ram-handler
This amounts to all the Poseidon files (probably several that don't need to be there) and the 3.9 modules (with some patches from Aminet applied). My machine is a 4000T, so your list will look a little different if you go this route. With these in place, I changed the SetPatch line in my startup-sequence to be C:SetPatch NOROMUPDATE QUIET. This allows the system to boot straight through without requiring the reboot after SetPatch usually loads in the ROM Update.
I think the old SCSI controller on the 2091 means you'll still be looking at a rather long boot, but this will probably save you a small chunk of time.
-
Ok, I have the following in my FlashROM:
romupdate.idtag
exec.library
denebpiousb.device
massstorage.class
serialcp210x.class
asixeth.class
pegasus.class
stir4200.class
palmpda.class
bluetooth.class
serialpl2303.class
printer.class
cdcacm.class
dm9601eth.class
ethwrap.class
rawwrap.class
moschipeth.class
poseidon.library
rtl8150eth.class
hub.class
input.device
hid.class
egalaxtouch.class
camdusbmidi.class
simplemidi.class
dfu.class
bootmouse.class
bootkeyboard.class
PsdStackLoader
NCR scsi.device
scsi.device
console.device
ptp.class
bootmenu
FastFileSystem
usbaudio.class
usbvideo.class
shell
ram-handler
This amounts to all the Poseidon files (probably several that don't need to be there) and the 3.9 modules (with some patches from Aminet applied). My machine is a 4000T, so your list will look a little different if you go this route. With these in place, I changed the SetPatch line in my startup-sequence to be C:SetPatch NOROMUPDATE QUIET. This allows the system to boot straight through without requiring the reboot after SetPatch usually loads in the ROM Update.
I think the old SCSI controller on the 2091 means you'll still be looking at a rather long boot, but this will probably save you a small chunk of time.
Thanks for that Matt. I'll have a go at tweaking my Deneb setup for my A4000.
-
Ok based on Matt_H's list I'm making the following comments for you to understand better :)
romupdate.idtag --> Needed. Exists on OS3.9 Update
exec.library--> Needed. Exists on OS3.9 Update
denebpiousb.device --> Since you use an A2000, you need instead the denebz2usb.device, but ONLY if you want USB support on boot
massstorage.class --> Needed only if you need to boot from USB on boot
serialcp210x.class --> Not needed
asixeth.class --> Not needed
pegasus.class --> Not needed
stir4200.class --> Not needed
palmpda.class --> Not needed
bluetooth.class --> Not needed
serialpl2303.class --> Not needed
printer.class --> Not needed
cdcacm.class --> Not needed
dm9601eth.class --> Not needed
ethwrap.class --> Not needed
rawwrap.class --> Not needed
moschipeth.class --> Not needed
poseidon.library --> Needed only if you want USB support on boot (storage, hid, etc)
rtl8150eth.class --> Not needed
hub.class --> Needed only if you want USB support on boot
input.device --> Needed only if you want USB support on boot (keyboard/mouse)
hid.class --> Needed only if you want USB support on boot (keyboard/mouse)
egalaxtouch.class --> Not needed
camdusbmidi.class --> Not needed
simplemidi.class --> Not needed
dfu.class --> Not needed
bootmouse.class --> Needed only if you want USB support on boot (keyboard/mouse)
bootkeyboard.class --> Needed only if you want USB support on boot (keyboard/mouse)
PsdStackLoader --> Needed if you want USB support and MUST be your saved config that works!
NCR scsi.device --> Not needed since you have an A2000
scsi.device --> Needed. Exists on OS3.9 Update
console.device --> Needed. Exists on OS3.9 Update
ptp.class --> Not needed
bootmenu --> Needed. Exists on OS3.9 Update
FastFileSystem --> Needed. Exists on OS3.9 Update
usbaudio.class --> Not needed
usbvideo.class --> Not needed
shell --> Needed. Exists on OS3.9 Update
ram-handler --> Needed. Exists on OS3.9 Update
Also you need as well:
Filesystem.resource --> Needed. Exists on OS3.9 Update
Optionaly you can put modules like:
NoClick --> Disables the mouse click noise
BBlank --> Disables the grey border putting a blank one (on native modes)
Much fun ahead :)
-
@ Mfilos:
So only the items in blue are essential to get rid of the OS3.9 "double boot"?
-
@Darrin
Aye mate. Since all modules are loaded from Flash, there is no need to get loaded again from the file "AmigaOS ROM Update" that resides in DEVS folder (via SetPatch).
Then you'd only need to do some alterations...
- First, edit your Startup-Sequence (make a backup copy just to be sure) and you need to replace the line of SetPatch with the following:
C:SetPatch NOROMUPDATE QUIET- Also (for safety reasons) you can rename the file "AmigaOS ROM Update" under DEVS to something else (for example: "AmigaOS ROM Update.bak").
- You're set :)
-
Thanks. I'll give it a go when I get back from this trip. It should shave a few seconds off my boot time. :)
-
Thanks very much fo the clarification. Unless this is going to significantly reduce my boot time (like in half or so), I may just leave well enough alone this time.
Right now I'm trying to get the Bridgeboard to play nice with the 2632. It appears that the Bridgeboard refuses to start unless you do the "2632" command after tclicking on the "PC Color" icon. My other project at the moment is to get Samba running, which is looking like the ocmputational equaivalent of landing a man on the moon.
But I guess if it was easy, everybody would be doing it :-)