dFlash 9.19(11.08.2013)
Thx @ gutemine
dFlash 9.19(11.08.2013)
Thx @ gutemine
dFlash 9.22 (11.08.2013)
Thx @ gutemine
dFlash 10.0.0
But all can whine and I tend to write pretty quickly what I need for inputs to isolate the fault
But anyway, if you really bland - on the first page is a first 10.0.0 test kit where you can tell me whether the progress bar is so useful .
But go for the first time only in the plugin in the web interface I'll kick it only when it works in the plugin.
And the length of the beam based on the assumption that will correspond to the space consumed m flash nfi about the future size - eg in Flodder is NOT correct and the bars never go to 100% before it is ready, but you first need to find out how much % it reaches a maximum before I can then customize .
But you will find it all out myself ... hopefully .
And since nothing else is new inside, except just start the new Releasezykuls and we are actually just test kits for the first time .
And like I said, if you used a Skinn where dFlash geskinned but is still without the new slider Skinnelement is the possibly not end well .
In OoZooN Image with default Skinn but it works
dFlash 11.0
Thx @ gutemine
dFlash 11.1
Thx @ gutemine
dFlash 12.2.7
12.2.7 from dFlash where the nfiwrite on the 8000 subpage and vid header gets set. But if that does not help the you can flash a 2.0 OE with OE 1.6 then slowly go out of my ideas. Basically, it would not be so bad because homogeneous flashing (ie 1.6 to 1.6 and 2.0 to 2.0) works so and to now I have the ONLY supported, but it would be a shame though, because it comes with the 7020HD yes.
Thx @ gutemine
dFlash 12.2.8 (2)
with new nfidump 0.11.18
Thx @ gutemine
dFlash 12.5 Release
Thx @ gutemine
Posting Permissions
Reply With Quote