Next Steps - More EXPERTISE needed...

[quenthal]

What kickstart version you are using with UAE?

[rkauer]

I think your best bet is reinstall the WB 3.0.

 Once you have a LEGAL Amiga to run it, it's ok to download a set of WB 3.0 disks and use it in the WinUAE in order to make your hd up and running again. Simply put the six images in the UAE virtual drives (df0: thru df5:)and boot from the install one (1st disk of the set).

[rkauer]

 BTW: keep your actual 68040.library (/me thinks you have a 68040 or 68060 CPU, the one supplied in the disks are a bit old, even incompatible with your H/W).

 And that's could a cause of the misbehaving of all things: you need the image ROM matchs your actual ROM and the processor choosed in emulation needs to be exactly the same, too.

 Bear in mind that are two different types of 3.0 ROMs: for A1200 and for A4000/A4000T.

[Mallette]

quenthal:  I reall don't know.  I am using 3.X on WinUAE, whatever that is.

rkauer:  I'll check it out.  I'll likely need some help.  There are lots of specialized files on Workbench (SimStation) that have to remain untouched.

Thanks to all...

[motorollin]

@rkauer
That link is illegal. Please remove it. Mallette has an email address in his profile, so if you want to provide him with links to illegal software you should send them that way instead of breakng the posting guidelines by posting a link.

Thanks

--
moto

[rkauer]

motorollin wrote:
@rkauer
That link is illegal. Please remove it. Mallette has an email address in his profile, so if you want to provide him with links to illegal software you should send them that way instead of breakng the posting guidelines by posting a link.

Thanks

--
moto

@Moto.

 As we discussed here before in many times: the link is only for WB 3.0 (original C= grab, not 3.1/3.5 or 3.9) and is intended for ppl who really have a 1200/4000, no use for other machines. And I don't hosted it.

 Sorry if anyway I offend this comunity doing this. The post was edited to remove the link, BTW.

[motorollin]

I have read (and participated in) the discussions about this before. However personal opinions on the distribution of copyrighted software do not change the posting guidelines of this site.

I appreciate you removing the link. Now lets not let this spiral in to another discussion about piracy and try to concentrate on helping Mallette :-)

--
moto

[Mallette]

Wish I'd followed it before it was removed.  I don't do piracy and I have a perfectly legal A4000.  

I've no problem with paying for things...there's precious little support left in the Amiga world anyway and no point in snuffing it out.

So...where do I get what I need?  I am assuming there is Workbench 3.something in WinUAE, but not sure what.  Also, since it won't boot to WB, I cannot verify exactly what version is in the A4000...though July, 1996 should be a pretty good clue.

[Mallette]

OK, no responses today.  Let's review...

My issue now is that SimStation will not boot.

If I boot WinUAE from the HDF file I made from SimStation it DOES boot to a CLI, but if I isse "loadwb" I get "invalid resident library."

So, Amiga gurus, what does that suggest?

Dave

[guru-666]

typical BS around here... sooner or later somebody claims something is illegal.. like we don't have real problems!

Then there is the group of people who always claim the Amiga just works and is simple. LOL Who are these people and have they ever used a modern computer?

the Amiga can be very hard to config and some option are confusing, on top of that ppl feel compelled to personally enforce the copy write on the OS3.0....(why, I will never know) rather and HELPING somebody use an Amiga.





 :lol:  :lol:  :quickdraw:

[mrbill]

BTW, I left CD-ROMs with Dave last weekend that have 1.3/2.x/3.x Kickstart ROMs on them, as well as a complete set of Workbench files from 1.x to 3.9.  

He should already have everything he needs for WinUAE.

(He owns a system with 3.x ROMs, and has physical copies of WorkBench 2.x and 3.x - I saw them myself)

I took pictures of his SimStation, you can find them here.

[rkauer]

 Ok, ppl.

 Moto has a valid point. I forget the guidelines of the board.

 Let's concentrate on Mallette's problem: the Simstation don't boot.

 I have an idea, but I may be wrong in the way it can be done: you can install SnoopDOS (aminet legal link) in the startup-sequence in order to catch the misbehaving library, then correct in dos mode only. :idea:

 But I'm unsure if snoopdos can run in dos mode only...

[motorollin]

@guru-666
Once again you have completely failed to see the point of my post. I expressed no personal opinion about the practicalities or morality of protecting ancient copyrights. I merely stated that it is against the terms and conditions of this site to spread copyrighted material. Fortunately rkauer is mature enough to realise this, and I respect him for that.

@rkauer
Yes, I think SnoopDOS will run in DOS, and that is a very good idea. But he would need to put "run" before it to allow him to return to the CLI prompt. Then the SnoopDOS log should show what library it is trying (and failing) to load.

--
moto

[Mallette]

Ok folks, we seem to be getting somewhere.  Will someone tell me PRECISELY what to change and where in the boot sequence to run the snooper?

I wish to proceed cautiously and attempt to fix only the items that have issues rather than a complete replacement.  SimStation has LOTS of very specialized libs and such that might be very difficult to identify and preserve.


Thanks in advance,
Dave

[Mallette]

Yes, I am replying to myself to bump this up higher, shamelessly...

Perhaps I should explain my last request in more detail:

1. Do I include the snoopster in my startup-sequence?
2. If so, with any switches?  Syntax for same?
3. Where do I look for the result after the bootup?

Dave

[Mallette]

Well, no reponses.  I worked at home the past two days on a very large software simulation so I was able to monitor things.  However, I am back "at the mill" for the next 7 days and so will likely restart where I left off then.  

I still need some input on how best to use SnoopDOS to locate the offending library.

Regards,
Dave