Welcome, Guest. Please login or register.

Author Topic: How to stop Deneb splash screen  (Read 9541 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Matt_H

Re: How to stop Deneb splash screen
« on: January 20, 2012, 10:56:09 PM »
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
 

Offline Matt_H

Re: How to stop Deneb splash screen
« Reply #1 on: January 22, 2012, 06:58:10 AM »
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.
 

Offline Matt_H

Re: How to stop Deneb splash screen
« Reply #2 on: January 23, 2012, 03:13:11 AM »
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!
 

Offline Matt_H

Re: How to stop Deneb splash screen
« Reply #3 on: January 24, 2012, 03:43:24 AM »
Quote from: Michele31415;677229
" 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 :)
 

Offline Matt_H

Re: How to stop Deneb splash screen
« Reply #4 on: January 25, 2012, 04:03:30 AM »
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 as well, but let's not introduce that variable just yet.
 

Offline Matt_H

Re: How to stop Deneb splash screen
« Reply #5 on: January 25, 2012, 10:55:45 PM »
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?
 

Offline Matt_H

Re: How to stop Deneb splash screen
« Reply #6 on: January 26, 2012, 12:43:28 AM »
Quote from: mfilos;677459
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 :)
 

Offline Matt_H

Re: How to stop Deneb splash screen
« Reply #7 on: January 26, 2012, 07:07:10 PM »
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.
 

Offline Matt_H

Re: How to stop Deneb splash screen
« Reply #8 on: January 27, 2012, 02:31:20 AM »
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.