»

[Michele31415]

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.

[mfilos]

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

[Michele31415]

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.

[Darrin]

Originally Posted by Michele31415

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).

[Matt_H]

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?

[mfilos]

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

[Matt_H]

Originally Posted by mfilos

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

[Michele31415]

Originally Posted by Matt_H

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.

[Tension]

Are you running 3.9? Sounds like your machine is resetting after applying SetPatch.

[mfilos]

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

[Michele31415]

Originally Posted by mfilos

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?

[Matt_H]

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.

[Michele31415]

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.

[Matt_H]

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.

[Darrin]

Originally Posted by Matt_H

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.