noob help with DENEB/Luciferin :)

Hi guys,

I just picked up a DENEB and was hoping to use it for a custom kickstart.

I desperately need help with how to set up the DENEB! :)

I've looked at a million tutorials and done more harm than good. I'd appreciate a dummy approach to this, if someone is helpful that doesn't mind teaching me!

I have classicwb, os3.9, bb1+2. I have an a4000T rom (no workbench.library) in an a4000D mobo. I have a mediator with voodoo3, fast ethernet, sb128. I also have a cocolino, fast ata mk v, and cv64/3d. My deneb is upgraded to v11. I have the old 3640.

Can someone please help me figure out what I need to flash onto the deneb?

Thanks! I have used REMUS to rip my 3.1 40.70 rom as well as the os3.9bb2 update rom. Thanks for the help.

If I throw all the contents of the 3.1 rom, the relevant contents of the 3.9/bb2 rom, what do I use for setpatch?

Also, what else can I throw in there? What can I put in to make the USB start on boot? And what libs/devs from the mediator (pci.library, etc) can I use as well? And also the cocolino drivers and fastata.driver.

Thanks for the help :)

Oh yeah - does it matter what order these files are in?? Can I put files from bb3/4 in there even if I haven't installed those?

Too many questions, so little time to answer them :P

OK lets get from the start first.
In order to be able to flash Deneb you need the program Luciferin that you can get from Chris Hodges website: http://www.platon42.de/files/usb/Luciferin.lha

The first time you'll run Luciferin it will ask you to extract the modules from your BB2 installation which you should agree with.
Once Luficerin is running, you'll see a window with 2 areas and some buttons and options on the lower right area.
- Left area = Your local files
- Right area = Tab with what you wanna put NOW in Deneb, Tab with Deneb's already stored content
- Lower right area = Buttons like Flash (which you click once you're ready) and some other options like making some modules only visible to OS3.9 or only to OS4.x etc.

So... you just need to locate the folder that was made upon start of Luciferin. IIRC it's on Luciferin/Modules/ROMUpdate folder. You only need to mark all modules and drag them to the right area (on the tab that is empty). After the drag and drop you should see all the ROM modules of 3.9 in the correct area ready to be flashed!

Just press the flash button and after some seconds you'll be ready :)
Power off and wait for 20secs and power on. Normally Deneb should have booted with the files you flashed (and will show some green flashing upon boot).

If everything works correctly, you can now remove the Startup-Sequence declarations of Setpatch setting only SetPatch NOROMUPDATE QUICK and renaming the file AmigaOS ROM Update under DEVS to something else.

That's all :)

@mfilos

Hi Marios, my friend :)

I'm using the BB4 update.... So I need only to flash with the updated device & libraries?

What about the LoadModule lines, ....? Just I need to comment these lines and write one SetPatch NOROMUPDATE QUICK in the startup-sequence?

All the best

Pablo

Pablo my friend...

Yes, you only need to insert the BB2 ROM Update modules plus the new versions (like fastfilesystem, scsi.device, console.device, shell-seg, datatypes.library etc...) from BB3 and BB4 to Deneb's flash!

Just to understand better what is happening with BB3 and BB4:
- The new versions of BB3/BB4, install some updated modules (like the ones I said 2 lines ago). Some of these libraries ALREADY exist on the AmigaOS ROM Update file (but in earlier versions).
By running the SetPatch line, the OS is seeking this file to load the modules inside it. Since you have newer files that will load with LoadModule, you'll get an error that these files are already loaded!
To avoid these errors, BB3/BB4's installation tells ya to alter the SetPatch command in order to skip these modules (via the SKIPROMMODULES declaration) for the newer ones to be able to load via LoadModule correctly!
- With Deneb you load every new module into the flash so you get the best parts from BB2/BB3/BB4 and put it in the flash.
- Since Deneb now has all the new modules... you DON'T need to skip any updates from SetPatch, and definitely DON'T need to load any module with LoadModules command.

So... if you load any new modules into Deneb's flash... you only need to:
- Comment the SetPatch line
- Comment the LoadModules line
- Insert a new SetPatch line instead with SetPatch NOROMUPDATE QUIET
- Just for safety... rename also the AmigaOS ROM Update file from Devs into something else (like AmigaOS ROM Update.bak)

I think it cleared a bit better some things :)

Marios, my friend.

Thanks a lot for this simple but perfect DENEB's guide. :thumbsup:

I will try this evening :)

Also when I reveice my new TOP3000 & EPROM's I want to read carefully your guide to burn real chips.... :)

Thanks again & my best wishes as allways

Pablo

Thanks Marios, I will testing this tonight on my A4000D :)

Thanks mfilos :) I think I have mission success! I also added the updated hsmathlibs, but using beta versions since I haven't paid yet. I took a look at: http://lilliput.amiga-projects.net/ROM_modules.htm and see that there are many updated kickstart modules that I'm not using. Is there a big advantage to use these? A lot of these things, I can't find...like Cosmos's custom 45.25 exec.library, for example.

Anyway, thanks for the help, works great! :)

Attachment 17265

Don't start putting Modules that you don't know just because they exist :)
Gulliver's list is awesome and for most modules you can get a pretty neat explanatory ReadMe file.

Just followed your guide Marios for both my A4k's and worked perfect, no more reboot :D

You're the man :thumbsup::bowdown: