How to use a newer 68040.library on a BPPC?

[Boot_WB]

Yes, the 68k libraries are resident in the flashrom of the bppc.

Silly question: have you set the option in the PPC startup menu to remap the rom to ram?

I have had this problem when using blizkick with bppc.  I also got an error when trying to start blizkick from the command line (regardless of whether the kickstart ROM is set to remap in the start menu).

I don't know how to solve it, except by removing blizkick from the startup sequence, and just using "BPPCFIX INSTALL 040" as the first line of the startup sequence.  Since setpatch resets your miggy anyway after installing there's no need for he extra reset command.

If you want to use other blizkick modules this won't help you i'm afraid.

[Boot_WB]

AmigaMance wrote:
@Boot_WB

Silly question: have you set the option in the PPC startup menu to remap the rom to ram?

 No, don't worry. ;-)

AFAIK you must have set the BPPC to remap the rom to ram to use blizkick.  Blizkick then patches the rom image (which now lies in ram), and all calls to rom functions are redirected to the memory address to which this image has been mapped (in my hazy understanding of blizkick).

Further silly questions: do you have the bppcfix and/or blizkick commands in your c: directory?  If not then calling them in your startup-sequence will probably crash the sequence.

Have you tried removing the 'QUIET' option from the setpatch line?  The debugging information can be quite useful in determining where in the startup sequence your system is freezing.

Also, if you are using SETPATCH NOROMUPDATES "scsi.device" make sure the NOROMUPDATES is in capitals.  

Don't know why BPPCFIX INSTALL 040 would cause your system to hang though.

[Boot_WB]

srg86 wrote:
nteresting, I just got a BPPC 040 and I've found that it's most stable with no 040 libraries at all.........snip........With no libs at all (BPPCFix) it just works.

@srg86 - there is no need to install anything in libs:.
 
A question should solve this: does everything works fine when you remove the BPPCFIX command completely?  

I believe the problem here may be some confusion over the command structure of BPPCFIX here:

The command BPPCFIX alone will remove ppc.library but leave the flashed 68040 library resident.

The command BPPCFIX 040 will remove both ppc.library and 68040.library.  In this case without a replacement (suitable) 68040.library in your LIBS: drawer you can expect the gurus you've been describing.

@Framiga There is no need for 'stub' or 'dummy' libraries with the 68040.  srg86 has the 040, not the 060 version.

@Nick - Your post is a little confusing - you are using "BPPCFIX 040", not "BPPCFIX040" aren't you?  The 040 is an optional switch - there is no BPPCFIX040 command to call, therefore calling this would not remove 68040.library, and it would also not remove ppc.library.

[Boot_WB]

itix wrote:
For me BPPCFix stopped working at some point. Or rather, it removed ppc.library but my BVision was gone as well.

I've just had to start with a fresh install after moving from Voodoo (Picasso96) to BVision (CGX) - just couldn't figure out what the problem was with my setup.  It all seems to be working ok now though.

Did you try using BPPCFIX >NIL: to prevent BPPCFIX opening a screen before startup-sequence loads the monitor drivers?  I'm not sure it makes a difference with the bvision, but it solved problems with "Intuition is attempting to blah-di-blah your screenmode" under Picasso96 (pain in the arse problem which meant changing the monitor output between Voodoo3 and AGA all the time when booting up).  I was so pleased when I figured that one out :-D


EDIT: 300 posts: all 8o11ock5 :lol:

[Boot_WB]

@Amigamance

I don't have it to hand, but as DoctorQ says it is pretty straightforward (same risk as a bios update on a PC) just don't pull the plug midway through.

Either that, or use the 040 switch after the BPPCfix command and install the newer 68040.library in your LIBS: drawer.