I am currently running the trial version of MorphOS in the hope that I can get everything configured correctly and running smoothly before I commit to buying the operating system and I have to say that I am having an extramly frustrating time trying to get rhlaunch to recognise any of my Kickstart 1.2 or 1.3 ROM files! I have tried every 1.2 and 1.3 ROM file I have, including 256k and 512k versions including the versions off Amiga Forever and the only ROM files that get recognised are the 2.0, 2.1, 3.0 and 3.1 Kickstart ROM's off the Amiga Forever pack.

What could I possibly be doing wrong? It's doing my head in.

[ Edited by madCrow 28.05.2014 - 17:46 ]

Quote:

Not sure, I've just tried here (setting the path preferences for Kickstart images in rhlaunch preferences) and it recognises the 256K 1,2 and 1,3 files without any problem.

Have you restarted rhlaunch since moving your ROM files? It seems to only scan the directory contents on startup, so if you've got rhlaunch open and are moving rom files into the directory, they won't be recognised until rhlaunch is restarted.

Maybe try to make configuration manually instead of using rhlaunch? I'm sure you can find a lot of info about euae configuration here on forum. I recommend to read that article also: click here

Maybe try Snoopium.(I think it's in tools/) It should report the paths that are being accessed and if access fails for some reason like a wrong path or filename.

Perhaps the Kickstart-Files are compressed.
rhLaunch unfortunately does not handle compressed files, yet.
Un-gzip the files for usage with rhLaunch.

Thing is, the path has to be correct as rhlaunch is recognising the other ROM's in the folder, it just refuses to recognise KS1.2 and 1.3 for some obscure reason?!

I've literally scoured the internet trying to find an image that rhlaunch will recognise but nothing will work.

Is it possible for someone to tell me step by step how to set up .ADF Mime types in the hope I can avoid using rhlaunch altogether? As a search highlights at least one other user on these forums having the same issue and I'm beginning to suspect a bug in the software - It just doesn't make sense.

Pampers, I've already tried following the steps in that linked article, but to be honest, trying to learn off an article translated using Google translate when you haven't used AmigaOS for about 20 odd years and you're very new to MorphOS is terribly difficult, some things just don't translate terribly well at all.

[ Edited by madCrow 29.05.2014 - 04:21 ]

> What could I possibly be doing wrong? It's doing my head in.

Well for example :
goto your ROM directory locate the not working roms right click to inspect the info rmation of the
file.
On the right hand you'll see :
readable
wrightable
executeable
deleteable

those 4 should be enabled - if not - than thats what is wrong.

good luck
(but sys:tools/snoopium would indeed have told you that earlier)

Checked permissions, everything looks ok....

http://i802.photobucket.com/albums/yy306/MattGatto/Grab_zps45a33cfe.jpg

Is Snoopium some form of debugger? Will give it a go after work this afternoon.

Anyone got a quick and easy guide to setting up Mime types for ADF files so I can launch them by simply double clicking on them?

Okay,

So I gave Snoopium a go, upon loading rhlaunch I see numerous issues, how do I make head or tail of what I'm seeing? (screenshot below).

Grab2_zps481618e2.jpg

I've saved the whole log but have no idea how to display it in the forums?

[ Edited by madCrow 30.05.2014 - 04:35 ]

Snoopium is like SnoopDOS on the older Amiga systems. Basically it traces and reports on a lot of information about what resources are being accessed by running applications. Most of the output isn't too useful but it you start RHLaunch, clear the log right before launching it with a 1.3 rom it could show if the file is being found and accessed at the right location. The portion in your screen shot shows it trying to access NListClass which is used for the GUI. Just because it failed a bunch of times doesn't mean anything because it's searching various locations for this class and probably finds it later on. Might be a good idea to make sure you have latest version of the class anyway.

Latest NList MUI Class:
http://sourceforge.net/projects/nlist-classes/

I just tried the program myself and I have a full set of Amiga Forever roms with the rom.key file
and it is unable to recognize any of them. Very odd.

[ Edited by realstar 29.05.2014 - 12:20 ]

Quote:

How weird is it?!

It's sooo annoying, I've been trying to work it out for days!

I wonder whether the author of rhlaunch frequents these forums?

>> I just tried the program myself and I have a full set of Amiga Forever roms
>> with the rom.key file and it is unable to recognize any of them. Very odd.

> How weird is it?! It's sooo annoying, I've been trying to work it out for days!

My take on this:

https://morph.zone/modules/newbb_plus/viewtopic.php?forum=3&topic_id=9553&start=42

> I wonder whether the author of rhlaunch frequents these forums?

"Last Login: 2014/4/12"
https://morph.zone/users/787.html

The odd thing is that my roms should be decrypted, I use them in FS-UAE under Linux and I'm sure FS-UAE decrypts them.

The other odd thing is that some of the Amiga Forever ROMS are working, just not KS1.2 and KS1.3.

Another odd thing is that I've tried so many different roms, even roms that aren't part of the Amiga Forever pack and none of the KS1.2 and 1.3 roms I try are working!

Got me stuffed, I'll just launch my old apps directly.

Quote:

Damn....Oh well...

[ Edited by madCrow 30.05.2014 - 15:03 ]

Ks1.2 and Ks1.3 files on my system are 256 kb big, so probably you have bad/wrong files.

Quote:

To quote my first post:

Quote:

The next thing is to drag my A500 out of storage and extract the KS roms off that, although I really can't be stuffed just so I can use rhlaunch....

One thing I have noticed is that out of 34 kickstarts rhlaunch is recognising only 5 even they are all of the same file type.

The file name has nothing to do with it also, one of the roms recognised by rhlaunch is kick20.rom, you can rename it to dogs_breakfast.rom and rhlaunch will still recognise it as kickstart 2.0.

I have no idea what method rhlaunch uses to recognise a file as a KS.rom, but it isn't working terribly well.

Quote:

> my roms should be decrypted, I use them in FS-UAE under Linux and I'm sure
> FS-UAE decrypts them.

It decrypts them in memory but does it really write them back to disk decrypted?

> The other odd thing is that some of the Amiga Forever ROMS are working, just not
> KS1.2 and KS1.3. Another odd thing is that I've tried so many different roms, even
> roms that aren't part of the Amiga Forever pack and none of the KS1.2 and 1.3 roms
> I try are working!

Odd indeed. I've no explanation for this, unfortunately.

Hi madCow,

I'm the author of rhLaunch.
It did not support encrypted amiga-forever roms until today.
Had some time and decided to do a quick fix:

http://www.219.dic.at/data/software/projects/rhLaunch/rhlaunch_fix.lha

Make sure you have the file "rom.key" in the same path where the *.rom-files are.


I'll do a full release later, have fun!

EDIT:
Version 0.7 is now available HERE. (MorphOS only)

Thanks a lot naTmeg for this fix for rhLaunch !!!

NaTmeg, you're awesome.

Will install in a little bit and give it a go.

Very impressed with the MorphOS community, as soon as I get the cash I'm purchasing my OS for sure!

Thank you all.

One question: do I install the file using the morphos installer?

[ Edited by madCrow 31.05.2014 - 05:52 ]

Quote:

In this case you just need to replace the older version of rhlaunch (just the single file).

Installer will process installation scripts, which are supplied with some software (it's usually pretty obvious if there is one, it'll usually be called 'Install' or 'foobar.install').

Have you tried Grunch btw (package manager which automates downloading/installing/updating)? The database of software is relatively limited compared to what is out there, but it's pretty near flawless in operation.

http://www.geit.de/eng_grunch.html

naTmeg the fix works a treat, thank you very much!

boot_wb, thank you for the advice on using the suplied file, I am familar with Grunch, the issue is that the time limited demo of MorphOS makes grunch difficult to use as by the time it's checked the repository's for updates you don't really get enough time to do much else before the system slows down (my internet could be faster!).

Thanks for the help people, as a long time Windows, Linux and AmigaOS user from a very long time ago I have to say that I am very impressed!

Now it's time to have a bit of a play on my overclocked Mac Mini....

[ Edited by madCrow 31.05.2014 - 08:50 ]

Thanks naTmeg. This new version fixed the rom issue for me as well.

Version 0.7 is now available HERE. (MorphOS only)