whats so special about 96940011?
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
Well ICS code isn't in this ROM... so that sux 
Looking for chunks of space that I can use... Trouble is this approach will probably net more errors and snafu's
oh well, I am really interested to find out what is in this rom that isn't in other 8's. ADC can't be it, must be something else
Looking for chunks of space that I can use... Trouble is this approach will probably net more errors and snafu's
oh well, I am really interested to find out what is in this rom that isn't in other 8's. ADC can't be it, must be something else
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
thanks.. damn its the same...
well this is getting worse and worse, the rom space that i was currently planning on using is actually being used in a block copy routine, in-efficient but thats life..
so now i have even less space to play with
well this is getting worse and worse, the rom space that i was currently planning on using is actually being used in a block copy routine, in-efficient but thats life..
so now i have even less space to play with
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
hrmm this is looking to be almost an impossible task - i really dont want to change the stock ecu bits too much, mainly because we don't have enough information about whats going on, and if we do something wrong it could be very bad
the problem is there isn't enough contiguous space to store the code and altmaps, i have found a redundant routine that almost gives me enough space if I kill it, but then I still need to find space for the maps...
really annoying, 96940011 has about 2k of freespace, and only about 500bytes is contigous, whereas 94170015 has like 10k of freespace and its all together
/waaaaaa
the problem is there isn't enough contiguous space to store the code and altmaps, i have found a redundant routine that almost gives me enough space if I kill it, but then I still need to find space for the maps...
really annoying, 96940011 has about 2k of freespace, and only about 500bytes is contigous, whereas 94170015 has like 10k of freespace and its all together
/waaaaaa
hrmm this is looking to be almost an impossible task - i really dont want to change the stock ecu bits too much, mainly because we don't have enough information about whats going on, and if we do something wrong it could be very bad
the problem is there isn't enough contiguous space to store the code and altmaps, i have found a redundant routine that almost gives me enough space if I kill it, but then I still need to find space for the maps...
really annoying, 96940011 has about 2k of freespace, and only about 500bytes is contigous, whereas 94170015 has like 10k of freespace and its all together
/waaaaaa
the problem is there isn't enough contiguous space to store the code and altmaps, i have found a redundant routine that almost gives me enough space if I kill it, but then I still need to find space for the maps...
really annoying, 96940011 has about 2k of freespace, and only about 500bytes is contigous, whereas 94170015 has like 10k of freespace and its all together
/waaaaaa
Aaron
At one time, I thought someone mentioned that the different ACD modes would cause timing changes.
I probably don't understand code and all the stuff well enough, but if in fact the ACD changes timing, wouldn't there be maps and a bunch of stuff related to that taking up space? Maybe that's the reason?
I probably don't understand code and all the stuff well enough, but if in fact the ACD changes timing, wouldn't there be maps and a bunch of stuff related to that taking up space? Maybe that's the reason?