Welcome, Guest. Please login or register.

Author Topic: execPrivate17()  (Read 2300 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Piru

  • \' union select name,pwd--
  • Hero Member
  • *****
  • Join Date: Aug 2002
  • Posts: 6946
    • Show all replies
    • http://www.iki.fi/sintonen/
Re: execPrivate17()
« on: December 11, 2004, 02:13:57 PM »
Quote
I found this out the hard way, trying to figure out why some roms I built combining 3.1 parts mixed with 3.9 parts wouldn`t boot.

How are you regenerating the relocs? Or are you just creating >512KB image and just zapping the matching 3.1 romtags?

I did this for BlizKick some years ago, and there I had to use some extra memory for the modules, since it would not fit 512K.
 

Offline Piru

  • \' union select name,pwd--
  • Hero Member
  • *****
  • Join Date: Aug 2002
  • Posts: 6946
    • Show all replies
    • http://www.iki.fi/sintonen/
Re: execPrivate17()
« Reply #1 on: December 12, 2004, 01:52:24 AM »
@Doobrey

Ok, this is pretty much what I did myself once, too. The problem was that there were quite a bit of cases I wasn't 100% sure about (reloc or data). In the end the "derelocated" rom never really worked fully.

If you manage to get it working, congratulations are in order. :-)