Sony Ericsson / Sony : Software, Firmware and Drivers : Danger: new firmware STILL has ms bug!
>
New Topic
>
Reply<
Esato Forum Index
>
Sony Ericsson / Sony >
Software, Firmware and Drivers
> Danger: new firmware STILL has ms bug!
Bookmark topic
@serg
That's right.....it should be a bug after all....but I'm not sure what caused it on your phone and my phone and not on other's phones....I hope SE don't let us down and take note of it to fix it ASAP!
For now, I'll have to revert back to the card reader.....
--
Posted: 2005-12-16 16:46:32
Edit :
Quote
I can confirm the "incorrect parameter" problem with my K750 also
System eventlog on my computer shows an EventID 51
Event Type: Warning
Event Source: Disk
Event Category: None
Event ID: 51
Date: 16-12-2005
Time: 08:29:17
User: N/A
Computer: NUMB
Description:
An error was detected on device DeviceHarddisk3D during a paging operation.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 03 01 68 00 01 00 b6 00 ..h...¶.
0008: 00 00 00 00 33 00 04 80 ....3..€
0010: 2d 01 00 00 0e 00 00 c0 -......À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 59 1a 01 00 00 00 00 00 Y.......
0030: ff ff ff ff 01 00 00 00 ÿÿÿÿ....
0038: 40 00 00 08 00 00 00 00 @.......
0040: ff 20 0c 12 4c 02 20 40 ÿ ..L. @
0048: 00 00 00 00 0a 00 00 00 ........
0050: 00 00 00 00 d8 3d 4d 86 ....Ø=M†
0058: 00 00 00 00 a8 01 a1 85 ....¨.¡…
0060: 00 00 00 00 80 9e 02 00 ....€ž..
0068: 28 00 00 02 9e 80 00 00 (...ž€..
0070: 80 00 00 00 00 00 00 00 €.......
0078: 00 00 00 00 00 00 00 00 ........
0080: 00 00 00 00 00 00 00 00 ........
0088: 00 00 00 00 00 00 00 00 ........
http://support.microsoft.com/[....]ee#XSLTH4126120123120121120120[ This Message was edited by: numb on 2005-12-16 17:23 ]
--
Posted: 2005-12-16 18:21:42
Edit :
Quote
@numb
Thanks for your findings! Now we can confirm that this is a bug and it is affecting to both k750 and w800. We can't really do much about it now, but have to wait till SE releases another firmware. I was actually impressed about everything else that the R1AA008 has changed. Hopefully SE developers are reading this thread and actually listening to us!
--
Posted: 2005-12-16 18:27:25
Edit :
Quote
Just tried switching to a different usb port, which auto reinstalled drivers again.
Tried copying the same amount of data from the ms duo again 2 times, havent failed yet.
Ill keep trying and see if I can provoke the error again.
Tried once more, but this time in the usb port that failed yesterday, this time no problems transfering.
I was extra carefull today making sure both cable and phone was well supported to avoid any strain on the cable and the connecting pins that might disconnect it.
If you have previously used it in more than one usb port, try connecting it to everyone and let it auto reinstall drivers for every usb port.
[ This Message was edited by: numb on 2005-12-16 17:47 ]
--
Posted: 2005-12-16 18:36:34
Edit :
Quote
... I think numb was bought by SE as a representative to not recognize a failure in a firmware release... LOL
just kidding man!
But how can you still say it's the cable!!! Think... it was working OK for everyone now complaining, they updated...; right the next second the cable will start to "unplug" itself from the connector so the error are coming from there?
See ya!
--
Posted: 2005-12-17 00:11:14
Edit :
Quote
Now if it is the cable, been knocked/slightly jarred and it's that easy to do, that it's now happening to quite a few people very often.
Then why is it that SE, use this very "hard to conect" cable, to update the phone?
I'm sure if the cable got unpluged that easy, there'd by loads of dead phones out there, due to the cable been unpluged duing update.
LETS FACE IT, IT'S A BUG. in the firmware. SE make mistakes. Everyone does. I mean this is only the 4th update I've had on my K750. My Laptop with windows XP was had 100+ and Microsoft still can't get that right.
--
Posted: 2005-12-17 00:23:26
Edit :
Quote
Just flashed R1AA008 ...
Copied a 200MB MP4 from MS to PC, result parameter error. I have a lab environment over here, so please exclude the cable connection crap. No, I'm not working for the competition
/JockyW
[ This Message was edited by: jockyw2001 on 2005-12-16 23:50 ]
--
Posted: 2005-12-17 00:47:24
Edit :
Quote
Im not saying its the cable.
If you read this thread you will see that I said the first mentioned "comunication error" was the cable.
This I have very physical evidense to support, and have described at several occations. I can disconnect and reconnect my phone simply by moving the connector up and down a few millimeter while plugged into its socket. Its not rocketscience to figure out that the pins then loose contact when I do this. For the same reason I am allways very carefull specifically in this are when I do my firmware updates, I dont move the phone or the cable and make sure both is well supported, which may be the reason why I never have "communication errors" during firmware updates, as so many others have reported during their firmware update.
I also said that the "incorrect parameter" error was a different error, this might very well be firmware, and it might be something else. I even posted the event ID and based on my years as computertechnician suggested to plug it into every usb port to let it reinstall the drivers, because the windows hardwareID was changed, which could induce conflicts leading to the "incorrect parameter" error.
Since doing this myself I have made more than 10 large filecopys to try and reintroduce the error, but have not been able to.
Im not saying its not a firmware error, Im only offering my personal observations as I go along. Everyone are free to make their own conlusions from this. And if people would rather spend days complaining than use 2 minuttes replugging the phone to all the usb ports, and make sure the cable is well seated in its socket while copying, just to see if it changes anything for them, then they are also free to do that.
I have no interest in defending S//E, I only have one interest, which is to try and figure out what causes this error, one good way of errorseeking is to rule out other possibilities of error, thus I try different things.
--
Posted: 2005-12-17 01:24:41
Edit :
Quote
@numb
Sorry my bad. You are right. I pluged it into an other usb and transfered over 400mb no probs. I've then tried plugging it back into the USB I use first and transfered the same folder again and thats upto 168mb, 3 times what I got after the upgrade.
Although I still think it's a bug of some sort, it's not a bad one. if all I have to do is use a differant USB port. Some uncapatabilaty, between windows and the way SEUS2 updates.
PS, just checked and the transfer is now upto 240mb on the first port. It may just be that all you have to do is unplug the USB cable and then plug it back in, if you have this problem.
--
Posted: 2005-12-17 02:34:03
Edit :
Quote
cheers! now we all agree upon on sumthin here...
here my hypothesis, since weve updated our SEUS services to SEUS2, maybe it had done sumthin with the drivers causing PC to be jiggy at one time. then if we reinstall those drivers then PC will stabilize at some point and wont consider the previous communication error a prob anymore. so thos whose havin communication error, can you confirm wot PC you are running.
mine is WinXP SP2: Pentium4 2.4GHz 256mb RAM, no probs from upgrade to file transfers phone to pc and vice versa. not a glitch. happy to be one of dem lucky fellas.
--
Posted: 2005-12-17 02:45:29
Edit :
Quote
New Topic
Reply
