Art didn't have time to do it himself, and when he released the source code, he specifically said that he doesn't want to see anyone making updates to X-Flash.Zitat:
Zitat von Joel Van
Printable View
Art didn't have time to do it himself, and when he released the source code, he specifically said that he doesn't want to see anyone making updates to X-Flash.Zitat:
Zitat von Joel Van
His code wasn't complicated, it was poorly commented and had ridiculous variable names. He stuff just about everything into one file. I looked at, anyone who attempts to mess with that, will have quite a party trying to figure out what the stuff does.Zitat:
Zitat von xploren
I suppose that's warranted, but bear in mind that it isn't rediculous to me, and it was never intended that anyone else ever see it.Zitat:
poorly commented and had ridiculous variable names
It is my guess that casual fly by nighters won't even be able to compile it
once any change is made, even though it's anti tamper mechanisms are now
in their face.
You can't simply remove the firmware checking.
The firmware check sets a bunch of variables that determine how the program will then operate..
ie. file addresses to modify are different depending on fw version.
The time I was talking about picking it up again myself is probably very far into the future, when far fewer people are still using PSPs.
It's possible that I could start a new job interstate at the end of next week, and have no regular PC or internet access for a
number of months (although there'll be PCs at work I can use since they want me to program).
Wow, sneaky :tup:
But then again, you could just hardcode the firmware variable..
Oh, Art, I was not trying to bash you at all. They were stating that it would be hard to tamper because it was complicated, when it truly is because the variables really only make sense to you. Sorry for the missunderstanding. :)Zitat:
Zitat von Art
three letter names for variables are a no no, and so is using global
variables throughout a program.. but that's largely to compensate for Human error on the programmer's end.
youresam is right, you could even add an extra routine to enter the firmware
code on a keyboard with the pikey keyboard program, or use an arcade style
letter rotator, figure out, or remove the anti tamper mechanism.. but newer
DAX firmwares wouldn't really be supported without adding new conditions
throughout the whole program to tell it where and what bytes to write for every
possible firmware.
-= Double Post =-
Oops, The anti tamper mechanism can't prevent changes in code .. what was I thinking?
It prevents changes to any of the in-built files, or at least if there is a change,
there is only 1 in 256 chance that it will work.
If any in-biult files are changed, you need to run X-Flash compiled with
calcsig set to 1, and then set setsig to the number you got from the PSP
when you ran the calcsig version on the PSP.
The calcsig variable was set back to 0 for the distribution version.
It might be easier to remove it.Code:void find_sig() {
calcsig = 0; // find ram signature if eaquals 1, skip for dist version if zero
sigset = 0x60 + 0x0F; // set ram signature to that found by calc sig routine (6F)
}
Another mechanism goes off if you use too much memory, and you have to increase
the allowable memory.
Just try to work on a version with support for 3.40 OE and add in extra features that other flashers dont have Like how you already have version spoofing
Dude, would you like it if you had a job of a lifetime and people force you to continue your project other than following your dreams? If you want it so much, learn coding at do it yourself.
I meant it as a suggestion . And coding is to confusing for me
No it is not. You just refuse to learn.Zitat:
Zitat von Fzero
Yes, exactly. Start with Lua and then to C and other languages. C is easier than you think. I learned it once.Zitat:
Zitat von PSPJunkie_
I strongly discourage the use of lua. Buy yourself a nice book on C or C++ and get reading.
i know you are have work and all, but, at least when you do an update, could you please add some secret-hidden-youhavetoknowaboutit way of forcing it to work? TT_TT
there are so many things that xflash can do, which other flashers can not, that i believe will work despite the fw difference....
please?
1) art says , that NOBODY may make updates of this , please respect that
2) not true
I'm trying to learn C but Beginner tutorials are really hard to understand
Eh? No they're not. Read the PSP-programming.com C tutorials. (ALL OF THEM.) That was all I needed to make PSPpaint (yes, a sucky program but still a product from a few simple tutorials).Zitat:
Zitat von Fzero
hallo, that's not really true. Art said he didn't want to see updates to this app that are crappy. He wants to see professional updates to the program so that X-Flash's reputation doesn't go down.
can anyone tell me which file is edited, when you disable WAVE effect with X-Flash??? thx!
I think it just flashes your current 0-12 to flash 1 so it works like a background
i don't remember EVER seeing my flash0's background files in my flash1...Zitat:
Zitat von Fzero
I assume it edits the system_plugin_bg for the wave, it must corrupt it.
delight1 : He means the background is copied to flash1, and he's true (not themes, backgrounds)
++ B.
When you set a background there is no more wave and the background is saved in flash1 , So what It would do is flash your current 0-12 to flash1
It would display the first BMP in 01-12.bmp...Zitat:
Zitat von Fzero
then tell me, how does it work in 1.50? that is why i do not think that would be how it works...Zitat:
Zitat von Fzero
I don't remember myself, but I think it's opening_plugin.rco.Zitat:
can anyone tell me which file is edited, when you disable WAVE effect
It wouldn't be hard to look at the source to be sure which file.
It's done by destroying the wave graphic, not by using a photo wallpaper as the background.
Maybe it just edits something in the wave that corrupts it then when it's enabled it edits it back to what the code used to be
thx i will have a lookZitat:
Zitat von Art
If your trying yo disable a wave try changing some text in a hex editor
If anyone with DAX Time Machine and 1.50 can start X-Flash V18k
without getting kicked out of the program, please let me know.
Also, if possible, I'd like a firmware dump done with the program emailed to me.
If it does start, I wouldn't suggest doing anything other than the firmware dump for the time being.
Cheers, Art.
Slim v2 /w 1.50+3.40HW = clash/lockup @ flash0 Space Used:Zitat:
Zitat von Art
Is it really checking flash0 (NAND) or my 4GB emulated "flash0"?
I tested psp filer and it also crash when switching to flash0, I think the emulation is too good, and the apps crash because of an overflow due to the 4GB "NAND"?
Not sure though, as I know nothing :)
It would really be checking space on flash0, but should kick you out before locking up.
That is the first time the program attempts to access flash, and only tries to
add the total of all file sizes for every file in flash0 partition.
If it has 1.50 kernel access it should have given some figure,
and maybe kicked you out rather than locking up.
I was planning a compatibility update rather than a feature update,
but at least nobody will be able to do any damage.
Art didn't you implement that "fw dump" safe mode for me earlier?
That should work with the time machine.
Yes you can use a firmware on MS, but it still has to access flash0
for one of the checks before it gets to the interface.
An update would have to check for Time Machine and probably won't
be allowed touch anything on the nand.
I have to disagree. I know this is an old post, but I feel the need to respond. Not everyone can program. The information will just not "soak up". Not everyone can think like a programmer ;)Zitat:
Zitat von PSPJunkie_
Hmm.... I didn't check too deep into DesCem's, but if it's still using the same flash emulation the original Pandora did (which I think due to "flashemu.prx") as long as the emulation is active, all app only see the memstick instead of the real thing when accessing flash0/flash1....Zitat:
Zitat von Art
I should be able to detect Time Machine in some way, and then skip any
flash0 access. Then there wouldn't be much work for me to do, just
pretend it's 1.50 on Memory Stick which it already has functionality for
(as mentioned).
I don't want to get stuck into this, it can't make me better,
it's better left in the past, available only to those with Time Machines ;)
I will be glad for that much so the work I did can last.
It's likely I will get a slim very soon, then I can bag it to hell without being
one of those people who were doing so only because they can't afford one.
Hehe...
Surely you could just do a certain check on say, an IPL? Like an MD5 check? I'm not sure if it's possible as I have absolutely no programming knowledge.Zitat:
Zitat von Art
Yes, it should be easy to do in many ways,
I'm only speculating because I will only do this with a slim,
and don't quite have it yet.
w00t, I finally got TM installed and running on my Slim :)
(had to temporarely put a 3.60 back on it for the dumping part....:dry: )
So, if you need some testing till getting your own Slim, drop me a line :)
(currently I have 1.50 and 3.60-M33 timemachine'ed :))
I'm talking sooner rather than later, like this week probably ;)
It'll be interesting to see what I would have done differently.
I know some things look funny to others, like seperate read and write
routines for every possible file that could be written, but there were
reasons for some of those things where mistakes couldn't be afforded.
Hey, they could have at least made that bubbly surface up near the USB port.
Less plastic would actually mean less money.