CD-RW 180 Firmware
Has anyone had any problems after flashing MSI CR52-M to latest firmware 1.80?
I also have a CR52-A2 which I flashed to 1.80D and that promptly led to refusal to read my CD-RWs. Luckily had a copy of the 1.61D firmware to flash back down to which fixed this.
However with the CR52-M, there's no way to backup the existing firmware before flashing. Hence my hesitation...
Yes, it's running on Ultra DMA 2...
By the way, I have the CD-RW on IDE2 in master and a DVD-ROM in lave (this one is running on PIO, can't understand why)
I read that link but don't you think it will be a little hard for me to "shout" every single characteristic of my computer and hardware and ehac version a definitions of that stuff? Lots of things I might say may not be needed at all so why can't you just ask what is needed to know and I'll be pleased to answer...
And seriously, I always try to write each of my posts in detail so I can get a fast answer without need to answre lost of questions first but I really don't know what else to say...
can't you just ask you want to know?
Similar Messages
-
NVIDIA driver won't load after running Radio Update
I have a mega 180 pc. I recently had some problems while installing virus protection sw. Long story short, I got it working again and tried running radio webupdate. I didn't know what it did but my computer rebooted and now no longer works correctly. I have restored most functionality with the exception of the following:
* Internet no longer works
* NVIDIA Geforce4 MX Integrated GPU will not load!
I consistenly get the following message when I try to load the driver
"error occurred during the installation of device"
"The required section was not found in the INF"
Any clue what is going on here and how I get this working again?
I have noticed a few comments that radio webupdate is a "firmware" update software that supposedly works over the internet. How can I tell which version of firmware I have?
If I try to re-install the firmware from "MEGA 180 Firmware 0C.zip" using a dos boot disk will this correct my problem?
Thanks, in advance...flash the old firmware back to the Bluebird module. i don't think there is an update for the Mega 180, the RadioWebUpdate utility was only for the 651 i believe
not sure how it would affect anything else though, but you might like to try a Repair install of Windows to see if it will fix it. there is a sticky in the Operating Systems forum with detailed instructions -
I have tagged on to some other Threads but thought it might be good to start another about this topic as I am sure I not the only one with this issue.
The main problem I have at the moment is slow responce time from the remote. This is very annouring as it is a cool looking remote and I would like to use it. Each button press takes about 1 second to be processed. I know it is not the Computer speed as when using the unit in the off state (only hi fi) it still takes a second for each button when entering in a radio station freq.
At the end of the day I after some answers, good or bad just so I know what can or can't be done.
Questions I have is.
Am I the only one with this?
Is this a issue with the 180 as well ?
Are the 180 and 865 LCD/Remote firmware the same ?
Can the Firmware 180 firmware fix this ?
System
Mega 865
Celeron 2.4 (soon to be a P4 2.8)
256 ram
XP proJust a short idea, doesn't the application to flash the newest firmware in the device use some sort of i2c communication? Maybe this app can somehow be used for other purposes also...
https://forum-en.msi.com/index.php?threadid=46355&sid=&hilight=firmware
They do something like this:
"i2cdown -b:3 -d:0xd0 -a:0xa4 -target:rom XXXXX.bin"
googled:
http://www.google.nl/search?q=i2cdown&ie=UTF-8&hl=nl&lr=
Heyz, sniffin' google i came across some info related to bluebird electronics. from 2004-01-01 they are called elgarelectronics:
http://elgarelectronics.co.uk/
they produce component to interact with LCD displays. Some kind of SDK might bring us a bit further into using the LCD, remote and radio hardware from within our own applications...
Lol, i have sendt these guys an email requesting info about an i2c component and the herefore required development tools.... Curious how this works out...
Greetings,
Peter Vrenken -
I need older firmware for laserjet 4250 V.33.21.FF Firmware Date code: 20100718 08.180.3
I have an HP laserjet 4250 and am looking for the following firmware if anyone has it let me know please.
V.33.21.FF Firmware Date code: 20100718 08.180.3http://ww2.cs.fsu.edu/~rosentha/linux/2.6.26.5/docs/DocBook/libata/ch07.html#excatATAbusErr wrote:
ATA bus error means that data corruption occurred during transmission over ATA bus (SATA or PATA). This type of errors can be indicated by
ICRC or ABRT error as described in the section called “ATA/ATAPI device error (non-NCQ / non-CHECK CONDITION)”.
Controller-specific error completion with error information indicating transmission error.
On some controllers, command timeout. In this case, there may be a mechanism to determine that the timeout is due to transmission error.
Unknown/random errors, timeouts and all sorts of weirdities.
As described above, transmission errors can cause wide variety of symptoms ranging from device ICRC error to random device lockup, and, for many cases, there is no way to tell if an error condition is due to transmission error or not; therefore, it's necessary to employ some kind of heuristic when dealing with errors and timeouts. For example, encountering repetitive ABRT errors for known supported command is likely to indicate ATA bus error.
Once it's determined that ATA bus errors have possibly occurred, lowering ATA bus transmission speed is one of actions which may alleviate the problem.
I'd also add; make sure you have good backups when ATA errors are frequent -
New MEGA 180 LCD firmware available (for trashed LCDs)
After a lot of hasteling of MSI they finally sent me some new firmware. I'm fairly sure it's not the BIOS, as the flashing procedure is very different. The LCD runs on firmware that is seperate from the BIOS, so this is probably it.
I can't try it till this evening, but would be interested if someone else can. I can email the firmware to anyone who needs to fix their thashed LCD. But I can't guarantee anything as I have not tried it myself.
I have the MEGA 180 boxed in the back of the car, ready to send off midday today, so would be very interested if anyone can test it before that.
If you want to try it, reply with your email address!I don't know much about this procedure, only that MSI sent me the above instructions and file to fix my LCD vanishing problem. The problem was due to running a welcome.exe application from the TV tuner CD. If this was not the cause of your problem it is posible that there is another problem and it can't be fixed like this.
I would at least expect the bxa0cms0.bin file to be opened and the flasher to fall over either when it is flashing, or to have to no effect.
In this case it sounds like there is a problem opening the bxa0cms0.bin file. Are you sure it is in the same location that you are executing the i2cdown flasher from? Has the extract of the zipped file worked OK? Can't think of anything else right now. -
Problem installing firmware 2.2 on first generation iPod touch 8GB
I recently tried to update my iPod touch from firmware 2.1 to 2.2. However, the install failed and restoring it (to 2.2) failed as well. On a different PC I tried the same. I managed to restore version 1.1.5 of the firmware on it. Unfortunately an upgrade to 2.2 failed on this PC as well.
The symptoms: the software is apparently unpacked correctly and downloaded to the device. However, during the verification stage, the iPod suddenly disconnects and reconnects and iTunes reports an error (error code 6).
Are there known issues with this firmware that can cause this?
Below is one of iPodUpdater log files:
2008-12-11 18:57:41.245 iTunes.exe[3108:b18]: restore library built Oct 24 2008 13:46:43
2008-12-11 18:57:41.245 iTunes.exe[3108:b18]: iTunes: iTunes 8.0.2.20
2008-12-11 18:57:41.245 iTunes.exe[3108:b18]: iTunes: Software payload version: 5G77
2008-12-11 18:57:41.808 iTunes.exe[3108:b18]: iTunes: Entering recovery mode, device 0X8967CF0
2008-12-11 18:57:44.764 iTunes.exe[3108:b18]: iTunes: received kAMDeviceDetached action, device 0X8967CF0
2008-12-11 18:57:50.316 iTunes.exe[3108:a1c]: WinAMRestore::OnInterfaceArrival: \\?\USB#VID05AC&PID1280#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB2103#6fd51fde
2008-12-11 18:57:50.332 iTunes.exe[3108:a1c]: WinAMRestore::AddAppleDeviceToDeviceList: \\?\USB#VID05AC&PID1280#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB2103#6fd51fde
2008-12-11 18:57:50.347 iTunes.exe[3108:a1c]: GetUsbSerialNumber: serial number descriptor does not exist
2008-12-11 18:57:50.363 iTunes.exe[3108:a1c]: AppleDevice::SetNotification: CONNECT, interface type: 1, id: \\?\USB#VID05AC&PID1280#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB2103#6fd51fde, inst: 0xaffb328
2008-12-11 18:57:50.363 iTunes.exe[3108:a1c]: WinAMRestore::AddAppleDeviceToDeviceList, empty list, new device
2008-12-11 18:57:50.363 iTunes.exe[3108:a1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x0affb328, notify: 1, connected: 0
2008-12-11 18:57:50.363 iTunes.exe[3108:a1c]: AppleDevice::NotifyConnect: Device type: 2, Interfaces total: 1, arrived: 1
2008-12-11 18:57:50.363 iTunes.exe[3108:a1c]: AppleDevice::NotifyConnect: IBOOT, IBOOT \\?\USB#VID05AC&PID1280#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB2103#6fd51fde, inst: 0xaffb328
2008-12-11 18:57:50.363 iTunes.exe[3108:b18]: iTunes: SCEP 3
2008-12-11 18:57:50.394 iTunes.exe[3108:bfc]: radio-error not set
2008-12-11 18:57:50.394 iTunes.exe[3108:bfc]: unable to open device_map.txt: No such file or directory
2008-12-11 18:57:50.394 iTunes.exe[3108:bfc]: <Recovery Mode Device 0820CF80>: operation 3 progress -1
2008-12-11 18:57:50.394 iTunes.exe[3108:bfc]: <Recovery Mode Device 0820CF80>: operation 4 progress -1
2008-12-11 18:57:50.410 iTunes.exe[3108:bfc]: bootstrapping restore with ***
2008-12-11 18:57:50.425 iTunes.exe[3108:bfc]: <Recovery Mode Device 0820CF80>: operation 31 progress -1
2008-12-11 18:57:51.426 iTunes.exe[3108:bfc]: <Recovery Mode Device 0820CF80>: Recovery mode succeeded
2008-12-11 18:57:56.071 iTunes.exe[3108:a1c]: WinAMRestore::OnInterfaceRemoval: \\?\USB#VID05AC&PID1280#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB2103#6fd51fde
2008-12-11 18:57:56.071 iTunes.exe[3108:a1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x0affb328, notify: 2, connected: 1
2008-12-11 18:57:56.071 iTunes.exe[3108:a1c]: AppleDevice::NotifyDisconnect: IBOOT, IBOOT \\?\USB#VID05AC&PID1280#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB2103#6fd51fde, inst: 0xaffb328
2008-12-11 18:57:56.103 iTunes.exe[3108:a1c]: _AMRecoveryModeDeviceFinalize: 0820CF80
2008-12-11 18:57:59.497 iTunes.exe[3108:a1c]: WinAMRestore::OnInterfaceArrival: \\?\USB#VID05AC&PID1281#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB0000#6fd51fde
2008-12-11 18:57:59.512 iTunes.exe[3108:a1c]: WinAMRestore::AddAppleDeviceToDeviceList: \\?\USB#VID05AC&PID1281#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB0000#6fd51fde
2008-12-11 18:57:59.528 iTunes.exe[3108:a1c]: AppleDevice::SetNotification: CONNECT, interface type: 1, id: \\?\USB#VID05AC&PID1281#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB0000#6fd51fde, inst: 0xaffb6d8
2008-12-11 18:57:59.528 iTunes.exe[3108:a1c]: WinAMRestore::AddAppleDeviceToDeviceList, new device
2008-12-11 18:57:59.528 iTunes.exe[3108:a1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x0affb328, notify: 0, connected: 0
2008-12-11 18:57:59.528 iTunes.exe[3108:a1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x0affb6d8, notify: 1, connected: 0
2008-12-11 18:57:59.528 iTunes.exe[3108:a1c]: AppleDevice::NotifyConnect: Device type: 2, Interfaces total: 2, arrived: 1
2008-12-11 18:57:59.528 iTunes.exe[3108:a1c]: AppleDevice::NotifyConnect: Interfaces total != arrived, no notification
2008-12-11 18:57:59.559 iTunes.exe[3108:a1c]: WinAMRestore::OnInterfaceArrival: \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#6fd51fde
2008-12-11 18:57:59.559 iTunes.exe[3108:a1c]: WinAMRestore::AddAppleDeviceToDeviceList: \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#6fd51fde
2008-12-11 18:57:59.575 iTunes.exe[3108:a1c]: WinAMRestore::AddAppleDeviceToDeviceList, device already connected, new interface
2008-12-11 18:57:59.575 iTunes.exe[3108:a1c]: AppleDevice::SetDeviceID: AMDINTERFACEDFU \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#6fd51fde, inst: 0xaffb6d8
2008-12-11 18:57:59.575 iTunes.exe[3108:a1c]: AppleDevice::SetNotification: CONNECT, interface type: 1, id: \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#6fd51fde, inst: 0xaffb6d8
2008-12-11 18:57:59.575 iTunes.exe[3108:a1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x0affb328, notify: 0, connected: 0
2008-12-11 18:57:59.575 iTunes.exe[3108:a1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x0affb6d8, notify: 1, connected: 1
2008-12-11 18:57:59.575 iTunes.exe[3108:a1c]: AppleDevice::NotifyConnect: Device type: 2, Interfaces total: 2, arrived: 2
2008-12-11 18:57:59.575 iTunes.exe[3108:a1c]: AppleDevice::NotifyConnect: IBOOT, IBOOT \\?\USB#VID05AC&PID1281#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB0000#6fd51fde, inst: 0xaffb6d8
2008-12-11 18:57:59.575 iTunes.exe[3108:a1c]: IBOOT, DFU \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#6fd51fde, inst: 0xaffb6d8
2008-12-11 18:57:59.590 iTunes.exe[3108:b18]: iTunes: SCEP 4
2008-12-11 18:57:59.606 iTunes.exe[3108:4ac]: AMDeviceIoControl: GetOverlappedResult failed
2008-12-11 18:57:59.606 iTunes.exe[3108:4ac]: ProcessOverlappedIoRequest: failed, error 31, usbd status c0000004
2008-12-11 18:58:00.106 iTunes.exe[3108:4ac]: AMDeviceIoControl: GetOverlappedResult failed
2008-12-11 18:58:00.106 iTunes.exe[3108:4ac]: ProcessOverlappedIoRequest: failed, error 31, usbd status c0000004
2008-12-11 18:58:00.607 iTunes.exe[3108:4ac]: AMDeviceIoControl: GetOverlappedResult failed
2008-12-11 18:58:00.607 iTunes.exe[3108:4ac]: ProcessOverlappedIoRequest: failed, error 31, usbd status c0000004
2008-12-11 18:58:01.107 iTunes.exe[3108:4ac]: USBControlTransfer: error 0, usbd status c0000004
2008-12-11 18:58:01.107 iTunes.exe[3108:4ac]: AMDeviceIoControl: GetOverlappedResult failed
2008-12-11 18:58:01.107 iTunes.exe[3108:4ac]: ProcessOverlappedIoRequest: failed, error 31, usbd status c0000004
2008-12-11 18:58:01.608 iTunes.exe[3108:4ac]: AMDeviceIoControl: GetOverlappedResult failed
2008-12-11 18:58:01.608 iTunes.exe[3108:4ac]: ProcessOverlappedIoRequest: failed, error 31, usbd status c0000004
2008-12-11 18:58:02.108 iTunes.exe[3108:4ac]: AMDeviceIoControl: GetOverlappedResult failed
2008-12-11 18:58:02.108 iTunes.exe[3108:4ac]: ProcessOverlappedIoRequest: failed, error 31, usbd status c0000004
2008-12-11 18:58:02.609 iTunes.exe[3108:4ac]: USBControlTransfer: error 0, usbd status c0000004
2008-12-11 18:58:02.609 iTunes.exe[3108:4ac]: radio-error not set
2008-12-11 18:58:02.625 iTunes.exe[3108:4ac]: unable to open device_map.txt: No such file or directory
2008-12-11 18:58:02.625 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 4 progress -1
2008-12-11 18:58:02.812 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 42 progress -1
2008-12-11 18:58:02.812 iTunes.exe[3108:4ac]: WinDFU::OpenDFUDevice: path: \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#6fd51fde
2008-12-11 18:58:02.812 iTunes.exe[3108:4ac]: WinDFU::OpenDeviceByPath: \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#6fd51fde
2008-12-11 18:58:02.812 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 42 progress 38
2008-12-11 18:58:02.812 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 42 progress 77
2008-12-11 18:58:02.812 iTunes.exe[3108:4ac]: WinDFU::UploadData: EOF, cbRead: 2436
2008-12-11 18:58:02.828 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 42 progress 100
2008-12-11 18:58:02.828 iTunes.exe[3108:4ac]: WinDFU::UploadData: ZLP
2008-12-11 18:58:02.828 iTunes.exe[3108:4ac]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
2008-12-11 18:58:02.828 iTunes.exe[3108:4ac]: WinDFU::ProcessUpdateState: status.bState == DFUSTATE_MANIFESTSYNC
2008-12-11 18:58:02.828 iTunes.exe[3108:4ac]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
2008-12-11 18:58:02.828 iTunes.exe[3108:4ac]: WinDFU::ProcessUpdateState: status.bState == DFUSTATEMANIFEST
2008-12-11 18:58:02.828 iTunes.exe[3108:4ac]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
2008-12-11 18:58:02.828 iTunes.exe[3108:4ac]: WinDFU::ProcessUpdateState: status.bState == DFUSTATE_MANIFEST_WAITRESET
2008-12-11 18:58:02.828 iTunes.exe[3108:4ac]: WinDFU::ResetDevice: resetting...
2008-12-11 18:58:03.203 iTunes.exe[3108:4ac]: WinDFU::FinalizeDfuUpdate: success
2008-12-11 18:58:04.267 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress -1
2008-12-11 18:58:04.267 iTunes.exe[3108:4ac]: WinDFU::OpenDFUDevice: path: \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#6fd51fde
2008-12-11 18:58:04.267 iTunes.exe[3108:4ac]: WinDFU::OpenDeviceByPath: \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#6fd51fde
2008-12-11 18:58:04.267 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 0
2008-12-11 18:58:04.533 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 1
2008-12-11 18:58:04.783 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 2
2008-12-11 18:58:05.096 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 3
2008-12-11 18:58:05.346 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 4
2008-12-11 18:58:05.612 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 5
2008-12-11 18:58:05.878 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 6
2008-12-11 18:58:06.143 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 7
2008-12-11 18:58:06.409 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 8
2008-12-11 18:58:06.660 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 9
2008-12-11 18:58:06.910 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 10
2008-12-11 18:58:07.176 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 11
2008-12-11 18:58:07.442 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 12
2008-12-11 18:58:07.692 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 13
2008-12-11 18:58:07.958 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 14
2008-12-11 18:58:08.224 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 15
2008-12-11 18:58:08.489 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 16
2008-12-11 18:58:08.755 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 17
2008-12-11 18:58:09.021 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 18
2008-12-11 18:58:09.287 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 19
2008-12-11 18:58:09.537 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 20
2008-12-11 18:58:09.803 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 21
2008-12-11 18:58:10.053 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 22
2008-12-11 18:58:10.319 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 23
2008-12-11 18:58:10.585 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 24
2008-12-11 18:58:10.851 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 25
2008-12-11 18:58:11.117 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 26
2008-12-11 18:58:11.383 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 27
2008-12-11 18:58:11.633 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 28
2008-12-11 18:58:11.899 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 29
2008-12-11 18:58:12.149 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 30
2008-12-11 18:58:12.415 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 31
2008-12-11 18:58:12.681 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 32
2008-12-11 18:58:12.947 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 33
2008-12-11 18:58:13.213 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 34
2008-12-11 18:58:13.479 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 35
2008-12-11 18:58:13.729 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 36
2008-12-11 18:58:13.995 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 37
2008-12-11 18:58:14.261 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 38
2008-12-11 18:58:14.511 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 39
2008-12-11 18:58:14.777 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 40
2008-12-11 18:58:15.043 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 41
2008-12-11 18:58:15.308 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 42
2008-12-11 18:58:15.574 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 43
2008-12-11 18:58:15.825 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 44
2008-12-11 18:58:16.090 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 45
2008-12-11 18:58:16.356 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 46
2008-12-11 18:58:16.622 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 47
2008-12-11 18:58:16.888 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 48
2008-12-11 18:58:17.154 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 49
2008-12-11 18:58:17.404 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 50
2008-12-11 18:58:17.670 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 51
2008-12-11 18:58:17.936 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 52
2008-12-11 18:58:18.186 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 53
2008-12-11 18:58:18.468 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 54
2008-12-11 18:58:18.718 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 55
2008-12-11 18:58:18.984 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 56
2008-12-11 18:58:19.250 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 57
2008-12-11 18:58:19.500 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 58
2008-12-11 18:58:19.766 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 59
2008-12-11 18:58:20.032 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 60
2008-12-11 18:58:20.298 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 61
2008-12-11 18:58:20.563 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 62
2008-12-11 18:58:20.814 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 63
2008-12-11 18:58:21.080 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 64
2008-12-11 18:58:21.330 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 65
2008-12-11 18:58:21.596 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 66
2008-12-11 18:58:21.862 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 67
2008-12-11 18:58:22.127 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 68
2008-12-11 18:58:22.393 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 69
2008-12-11 18:58:22.644 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 70
2008-12-11 18:58:22.909 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 71
2008-12-11 18:58:23.175 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 72
2008-12-11 18:58:23.426 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 73
2008-12-11 18:58:23.691 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 74
2008-12-11 18:58:23.957 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 75
2008-12-11 18:58:24.223 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 76
2008-12-11 18:58:24.489 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 77
2008-12-11 18:58:24.739 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 78
2008-12-11 18:58:25.005 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 79
2008-12-11 18:58:25.287 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 80
2008-12-11 18:58:25.553 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 81
2008-12-11 18:58:25.803 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 82
2008-12-11 18:58:26.069 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 83
2008-12-11 18:58:26.335 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 84
2008-12-11 18:58:26.600 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 85
2008-12-11 18:58:26.866 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 86
2008-12-11 18:58:27.117 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 87
2008-12-11 18:58:27.382 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 88
2008-12-11 18:58:27.648 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 89
2008-12-11 18:58:27.914 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 90
2008-12-11 18:58:28.180 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 91
2008-12-11 18:58:28.446 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 92
2008-12-11 18:58:28.712 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 93
2008-12-11 18:58:28.978 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 94
2008-12-11 18:58:29.244 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 95
2008-12-11 18:58:29.494 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 96
2008-12-11 18:58:29.760 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 97
2008-12-11 18:58:30.026 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 98
2008-12-11 18:58:30.292 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 99
2008-12-11 18:58:30.542 iTunes.exe[3108:4ac]: WinDFU::UploadData: EOF, cbRead: 3368
2008-12-11 18:58:30.557 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 5 progress 100
2008-12-11 18:58:30.557 iTunes.exe[3108:4ac]: WinDFU::UploadData: ZLP
2008-12-11 18:58:30.557 iTunes.exe[3108:4ac]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
2008-12-11 18:58:30.557 iTunes.exe[3108:4ac]: WinDFU::ProcessUpdateState: status.bState == DFUSTATE_MANIFESTSYNC
2008-12-11 18:58:30.557 iTunes.exe[3108:4ac]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
2008-12-11 18:58:30.557 iTunes.exe[3108:4ac]: WinDFU::ProcessUpdateState: status.bState == DFUSTATEMANIFEST
2008-12-11 18:58:30.557 iTunes.exe[3108:4ac]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
2008-12-11 18:58:30.557 iTunes.exe[3108:4ac]: WinDFU::ProcessUpdateState: status.bState == DFUSTATE_MANIFEST_WAITRESET
2008-12-11 18:58:30.557 iTunes.exe[3108:4ac]: WinDFU::ResetDevice: resetting...
2008-12-11 18:58:30.933 iTunes.exe[3108:4ac]: WinDFU::FinalizeDfuUpdate: success
2008-12-11 18:58:34.295 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 6 progress -1
2008-12-11 18:58:34.295 iTunes.exe[3108:4ac]: WinDFU::OpenDFUDevice: path: \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#6fd51fde
2008-12-11 18:58:34.295 iTunes.exe[3108:4ac]: WinDFU::OpenDeviceByPath: \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#6fd51fde
2008-12-11 18:58:34.311 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 6 progress 11
2008-12-11 18:58:34.311 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 6 progress 22
2008-12-11 18:58:34.311 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 6 progress 33
2008-12-11 18:58:34.311 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 6 progress 44
2008-12-11 18:58:34.327 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 6 progress 55
2008-12-11 18:58:34.327 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 6 progress 66
2008-12-11 18:58:34.327 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 6 progress 77
2008-12-11 18:58:34.342 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 6 progress 88
2008-12-11 18:58:34.342 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 6 progress 99
2008-12-11 18:58:34.342 iTunes.exe[3108:4ac]: WinDFU::UploadData: EOF, cbRead: 336
2008-12-11 18:58:34.342 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 6 progress 100
2008-12-11 18:58:34.342 iTunes.exe[3108:4ac]: WinDFU::UploadData: ZLP
2008-12-11 18:58:34.342 iTunes.exe[3108:4ac]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
2008-12-11 18:58:34.342 iTunes.exe[3108:4ac]: WinDFU::ProcessUpdateState: status.bState == DFUSTATE_MANIFESTSYNC
2008-12-11 18:58:34.342 iTunes.exe[3108:4ac]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
2008-12-11 18:58:34.342 iTunes.exe[3108:4ac]: WinDFU::ProcessUpdateState: status.bState == DFUSTATEMANIFEST
2008-12-11 18:58:34.342 iTunes.exe[3108:4ac]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
2008-12-11 18:58:34.342 iTunes.exe[3108:4ac]: WinDFU::ProcessUpdateState: status.bState == DFUSTATE_MANIFEST_WAITRESET
2008-12-11 18:58:34.342 iTunes.exe[3108:4ac]: WinDFU::ResetDevice: resetting...
2008-12-11 18:58:34.733 iTunes.exe[3108:4ac]: WinDFU::FinalizeDfuUpdate: success
2008-12-11 18:58:35.734 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress -1
2008-12-11 18:58:35.734 iTunes.exe[3108:4ac]: WinDFU::OpenDFUDevice: path: \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#6fd51fde
2008-12-11 18:58:35.734 iTunes.exe[3108:4ac]: WinDFU::OpenDeviceByPath: \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#6fd51fde
2008-12-11 18:58:35.750 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 0
2008-12-11 18:58:35.781 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 1
2008-12-11 18:58:35.828 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 2
2008-12-11 18:58:35.875 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 3
2008-12-11 18:58:35.906 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 4
2008-12-11 18:58:35.953 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 5
2008-12-11 18:58:35.984 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 6
2008-12-11 18:58:36.031 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 7
2008-12-11 18:58:36.078 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 8
2008-12-11 18:58:36.110 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 9
2008-12-11 18:58:36.156 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 10
2008-12-11 18:58:36.188 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 11
2008-12-11 18:58:36.235 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 12
2008-12-11 18:58:36.266 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 13
2008-12-11 18:58:36.313 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 14
2008-12-11 18:58:36.360 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 15
2008-12-11 18:58:36.391 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 16
2008-12-11 18:58:36.438 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 17
2008-12-11 18:58:36.485 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 18
2008-12-11 18:58:36.516 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 19
2008-12-11 18:58:36.563 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 20
2008-12-11 18:58:36.594 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 21
2008-12-11 18:58:36.641 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 22
2008-12-11 18:58:36.688 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 23
2008-12-11 18:58:36.720 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 24
2008-12-11 18:58:36.766 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 25
2008-12-11 18:58:36.798 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 26
2008-12-11 18:58:36.829 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 27
2008-12-11 18:58:36.876 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 28
2008-12-11 18:58:36.923 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 29
2008-12-11 18:58:36.954 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 30
2008-12-11 18:58:37.001 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 31
2008-12-11 18:58:37.048 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 32
2008-12-11 18:58:37.079 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 33
2008-12-11 18:58:37.126 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 34
2008-12-11 18:58:37.157 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 35
2008-12-11 18:58:37.204 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 36
2008-12-11 18:58:37.236 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 37
2008-12-11 18:58:37.283 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 38
2008-12-11 18:58:37.329 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 39
2008-12-11 18:58:37.376 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 40
2008-12-11 18:58:37.408 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 41
2008-12-11 18:58:37.455 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 42
2008-12-11 18:58:37.501 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 43
2008-12-11 18:58:37.533 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 44
2008-12-11 18:58:37.580 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 45
2008-12-11 18:58:37.627 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 46
2008-12-11 18:58:37.658 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 47
2008-12-11 18:58:37.705 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 48
2008-12-11 18:58:37.736 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 49
2008-12-11 18:58:37.783 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 50
2008-12-11 18:58:37.814 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 51
2008-12-11 18:58:37.861 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 52
2008-12-11 18:58:37.892 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 53
2008-12-11 18:58:37.939 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 54
2008-12-11 18:58:37.986 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 55
2008-12-11 18:58:38.033 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 56
2008-12-11 18:58:38.065 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 57
2008-12-11 18:58:38.111 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 58
2008-12-11 18:58:38.158 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 59
2008-12-11 18:58:38.190 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 60
2008-12-11 18:58:38.237 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 61
2008-12-11 18:58:38.268 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 62
2008-12-11 18:58:38.315 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 63
2008-12-11 18:58:38.362 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 64
2008-12-11 18:58:38.393 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 65
2008-12-11 18:58:38.440 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 66
2008-12-11 18:58:38.471 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 67
2008-12-11 18:58:38.518 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 68
2008-12-11 18:58:38.565 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 69
2008-12-11 18:58:38.596 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 70
2008-12-11 18:58:38.643 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 71
2008-12-11 18:58:38.674 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 72
2008-12-11 18:58:38.721 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 73
2008-12-11 18:58:38.768 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 74
2008-12-11 18:58:38.800 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 75
2008-12-11 18:58:38.847 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 76
2008-12-11 18:58:38.878 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 77
2008-12-11 18:58:38.925 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 78
2008-12-11 18:58:38.956 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 79
2008-12-11 18:58:39.003 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 80
2008-12-11 18:58:39.050 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 81
2008-12-11 18:58:39.081 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 82
2008-12-11 18:58:39.128 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 83
2008-12-11 18:58:39.159 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 84
2008-12-11 18:58:39.206 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 85
2008-12-11 18:58:39.238 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 86
2008-12-11 18:58:39.284 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 87
2008-12-11 18:58:39.316 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 88
2008-12-11 18:58:39.363 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 89
2008-12-11 18:58:39.394 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 90
2008-12-11 18:58:39.441 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 91
2008-12-11 18:58:39.488 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 92
2008-12-11 18:58:39.519 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 93
2008-12-11 18:58:39.566 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 94
2008-12-11 18:58:39.597 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 95
2008-12-11 18:58:39.644 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 96
2008-12-11 18:58:39.675 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 97
2008-12-11 18:58:39.722 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 98
2008-12-11 18:58:39.754 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 99
2008-12-11 18:58:39.801 iTunes.exe[3108:4ac]: WinDFU::UploadData: EOF, cbRead: 356
2008-12-11 18:58:39.801 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 7 progress 100
2008-12-11 18:58:39.801 iTunes.exe[3108:4ac]: WinDFU::UploadData: ZLP
2008-12-11 18:58:39.801 iTunes.exe[3108:4ac]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
2008-12-11 18:58:39.801 iTunes.exe[3108:4ac]: WinDFU::ProcessUpdateState: status.bState == DFUSTATE_MANIFESTSYNC
2008-12-11 18:58:39.801 iTunes.exe[3108:4ac]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
2008-12-11 18:58:39.801 iTunes.exe[3108:4ac]: WinDFU::ProcessUpdateState: status.bState == DFUSTATEMANIFEST
2008-12-11 18:58:39.801 iTunes.exe[3108:4ac]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
2008-12-11 18:58:39.801 iTunes.exe[3108:4ac]: WinDFU::ProcessUpdateState: status.bState == DFUSTATE_MANIFEST_WAITRESET
2008-12-11 18:58:39.801 iTunes.exe[3108:4ac]: WinDFU::ResetDevice: resetting...
2008-12-11 18:58:40.192 iTunes.exe[3108:4ac]: WinDFU::FinalizeDfuUpdate: success
2008-12-11 18:58:40.192 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 8 progress -1
2008-12-11 18:58:40.192 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: operation 9 progress -1
2008-12-11 18:58:40.192 iTunes.exe[3108:4ac]: <Recovery Mode Device 0820CF80>: Recovery mode succeeded
2008-12-11 18:58:41.787 iTunes.exe[3108:a1c]: WinAMRestore::OnInterfaceRemoval: \\?\USB#VID05AC&PID1281#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB0000#6fd51fde
2008-12-11 18:58:41.802 iTunes.exe[3108:a1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x0affb328, notify: 2, connected: 0
2008-12-11 18:58:41.802 iTunes.exe[3108:a1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x0affb6d8, notify: 2, connected: 1
2008-12-11 18:58:41.802 iTunes.exe[3108:a1c]: AppleDevice::NotifyDisconnect: IBOOT, IBOOT \\?\USB#VID05AC&PID1281#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB0000#6fd51fde, inst: 0xaffb6d8
2008-12-11 18:58:41.802 iTunes.exe[3108:a1c]: IBOOT, DFU \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#6fd51fde, inst: 0xaffb6d8
2008-12-11 18:58:41.818 iTunes.exe[3108:a1c]: _AMRecoveryModeDeviceFinalize: 0820CF80
2008-12-11 18:58:41.834 iTunes.exe[3108:a1c]: WinAMRestore::OnInterfaceRemoval: \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#6fd51fde
2008-12-11 18:58:41.834 iTunes.exe[3108:a1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x0affb328, notify: 2, connected: 0
2008-12-11 18:58:41.834 iTunes.exe[3108:a1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x0affb6d8, notify: 2, connected: 0
2008-12-11 18:58:45.040 iTunes.exe[3108:b18]: iTunes: received kAMDeviceAttached action, device 0XAFFBCA0, AFC error 0XE8000028
2008-12-11 18:58:45.040 iTunes.exe[3108:b18]: iTunes: Restore mode device appeared, device 0XAFFBCA0
2008-12-11 18:58:45.040 iTunes.exe[3108:b18]: iTunes: Creating restore mode device with usbMuxDeviceID 0X2
2008-12-11 18:58:45.040 iTunes.exe[3108:b18]: <Restore Device 08142208>: operation 3 progress -1
2008-12-11 18:58:45.040 iTunes.exe[3108:b18]: <Restore Device 08142208>: operation 4 progress -1
2008-12-11 18:58:45.056 iTunes.exe[3108:b18]: Supports value queries: 1
2008-12-11 18:58:45.087 iTunes.exe[3108:9ec]: device did not return saved USB log
2008-12-11 18:58:45.087 iTunes.exe[3108:9ec]: device did not return saved panic log
2008-12-11 18:58:45.087 iTunes.exe[3108:9ec]: connected to service com.apple.mobile.restored
2008-12-11 18:58:45.087 iTunes.exe[3108:9ec]: using protocol version 11
2008-12-11 18:58:45.102 iTunes.exe[3108:9ec]: unable to open device_map.txt: No such file or directory
2008-12-11 18:58:45.102 iTunes.exe[3108:9ec]: board config = n45ap
2008-12-11 18:58:45.102 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 28 progress -1
2008-12-11 18:58:45.118 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 11 progress -1
2008-12-11 18:58:45.900 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 12 progress -1
2008-12-11 19:04:47.469 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 12 progress -1
2008-12-11 19:04:54.722 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 0
2008-12-11 19:05:04.741 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 1
2008-12-11 19:05:12.384 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 5
2008-12-11 19:05:12.681 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 6
2008-12-11 19:05:13.041 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 7
2008-12-11 19:05:18.589 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 8
2008-12-11 19:05:20.465 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 9
2008-12-11 19:05:22.622 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 10
2008-12-11 19:05:23.513 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 11
2008-12-11 19:05:25.123 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 12
2008-12-11 19:05:26.404 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 13
2008-12-11 19:05:27.514 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 14
2008-12-11 19:05:28.077 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 15
2008-12-11 19:05:28.999 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 16
2008-12-11 19:05:29.718 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 17
2008-12-11 19:05:31.578 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 18
2008-12-11 19:05:33.219 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 19
2008-12-11 19:05:34.642 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 20
2008-12-11 19:05:35.658 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 21
2008-12-11 19:05:36.674 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 22
2008-12-11 19:05:37.705 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 23
2008-12-11 19:05:39.643 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 24
2008-12-11 19:05:40.237 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 25
2008-12-11 19:05:41.519 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 26
2008-12-11 19:05:42.347 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 27
2008-12-11 19:05:43.566 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 28
2008-12-11 19:05:44.942 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 29
2008-12-11 19:05:45.817 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 30
2008-12-11 19:05:46.974 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 31
2008-12-11 19:05:48.287 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 32
2008-12-11 19:05:49.365 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 33
2008-12-11 19:05:50.288 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 34
2008-12-11 19:05:51.554 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 35
2008-12-11 19:05:52.820 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 36
2008-12-11 19:05:54.398 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 37
2008-12-11 19:05:55.320 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 38
2008-12-11 19:05:56.696 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 39
2008-12-11 19:05:58.009 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 40
2008-12-11 19:05:59.166 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 41
2008-12-11 19:06:00.322 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 42
2008-12-11 19:06:01.463 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 43
2008-12-11 19:06:02.542 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 44
2008-12-11 19:06:04.589 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 45
2008-12-11 19:06:06.012 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 46
2008-12-11 19:06:07.356 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 47
2008-12-11 19:06:08.778 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 48
2008-12-11 19:06:09.450 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 49
2008-12-11 19:06:10.466 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 50
2008-12-11 19:06:11.091 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 51
2008-12-11 19:06:12.091 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 52
2008-12-11 19:06:13.529 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 53
2008-12-11 19:06:15.076 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 54
2008-12-11 19:06:16.467 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 55
2008-12-11 19:06:17.764 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 56
2008-12-11 19:06:18.951 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 57
2008-12-11 19:06:20.311 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 58
2008-12-11 19:06:21.670 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 59
2008-12-11 19:06:22.967 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 60
2008-12-11 19:06:24.436 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 61
2008-12-11 19:06:25.265 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 62
2008-12-11 19:06:27.109 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 63
2008-12-11 19:06:28.390 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 64
2008-12-11 19:06:29.546 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 65
2008-12-11 19:06:30.953 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 66
2008-12-11 19:06:32.687 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 67
2008-12-11 19:06:33.938 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 68
2008-12-11 19:06:34.969 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 69
2008-12-11 19:06:36.453 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 70
2008-12-11 19:06:37.610 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 71
2008-12-11 19:06:40.892 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 72
2008-12-11 19:06:44.204 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 73
2008-12-11 19:06:45.283 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 74
2008-12-11 19:06:46.330 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 75
2008-12-11 19:06:48.283 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 76
2008-12-11 19:06:49.940 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 77
2008-12-11 19:06:51.815 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 78
2008-12-11 19:06:52.596 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 79
2008-12-11 19:06:54.284 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 80
2008-12-11 19:06:55.472 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 81
2008-12-11 19:06:56.394 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 82
2008-12-11 19:06:57.816 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 83
2008-12-11 19:06:59.675 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 84
2008-12-11 19:07:01.019 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 85
2008-12-11 19:07:02.551 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 86
2008-12-11 19:07:04.488 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 87
2008-12-11 19:07:05.285 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 88
2008-12-11 19:07:07.051 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 89
2008-12-11 19:07:08.348 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 90
2008-12-11 19:07:10.661 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 91
2008-12-11 19:07:13.302 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 92
2008-12-11 19:07:17.537 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 93
2008-12-11 19:07:19.584 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 94
2008-12-11 19:07:20.819 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 95
2008-12-11 19:07:22.178 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 96
2008-12-11 19:07:24.131 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 97
2008-12-11 19:07:25.788 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 98
2008-12-11 19:07:27.726 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 13 progress 100
2008-12-11 19:07:27.726 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 14 progress -1
2008-12-11 19:08:45.142 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 15 progress -1
2008-12-11 19:08:50.486 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 16 progress -1
2008-12-11 19:08:50.533 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 15 progress -1
2008-12-11 19:08:50.674 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 16 progress -1
2008-12-11 19:08:56.393 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 17 progress -1
2008-12-11 19:08:56.612 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 29 progress -1
2008-12-11 19:08:56.925 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 29 progress -1
2008-12-11 19:08:56.956 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 25 progress -1
2008-12-11 19:08:56.987 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 35 progress -1
2008-12-11 19:08:57.331 iTunes.exe[3108:9ec]: <Restore Device 08142208>: operation 18 progress -1
2008-12-11 19:09:05.394 iTunes.exe[3108:9ec]: device returned AMR error 6
2008-12-11 19:09:05.394 iTunes.exe[3108:9ec]:
==== device restore output ====
found suitable IOMobileFramebuffer: AppleH1CLCD
=100
AppleMRVL868x: mrvl.ps.multicast_timeout=10
AppleMRVL868x: mrvl.ps.entrance_timeout=15
AppleMRVL868x: marvell-powersave-listenint=1
AppleMRVL868x: marvell-retry-limit=15
AppleMRVL868x: marvell-sdio-pulldowns=-1
AppleMRVL868x: WTE=0x0
AppleMRVL868x::setPowerStateGated(): 0 -> 1, 0xc23b5000
AppleMRVL868x: Loading Main Program
AppleMRVL868x: Firmware loaded.
substituting fake sdio local-mac-address for N45
unable to find bluetooth service
unable to find baseband service
unable to get device IMEI
AppleSynopsysOTG2 - Configuration: PTP
AppleSynopsysOTG2 Interface: PTP
AppleSynopsysOTG2 - Configuration: iPod USB Interface
AppleSynopsysOTG2 Interface: USBAudioControl
AppleSynopsysOTG2 Interface: USBAudioStreaming
AppleSynopsysOTG2 Interface: IapOverUsbHid
AppleSynopsysOTG2 - Configuration: PTP + Apple Mobile Device
AppleSynopsysOTG2 Interface: PTP
AppleSynopsysOTG2 Interface: AppleUSBMux
AppleSynopsysOTG2::gated_registerFunction Register function USBAudioControl
IOAccessoryPortUSB::start
AppleSynopsysOTG2::gated_registerFunction Register function IapOverUsbHid
AppleSynopsysOTG2::gated_registerFunction Register function USBAudioStreaming
virtual bool AppleUSBDeviceMux::start(IOService*) build: Nov 1 2008 19:56:14
init_waste
AppleSynopsysOTG2::gated_registerFunction Register function AppleUSBMux
AppleSynopsysOTG2::gated_registerFunction Register function PTP
AppleSynopsysOTG2::gated_registerFunction all functions registered- we are ready to start usb stack
AppleSynopsysOTG2::handleUSBReset
virtual IOReturn AppleUSBDeviceMux::setProperties(OSObject*) setting debug level to 1
AppleSynopsysOTG2::handleUSBReset
AppleMRVL868x Hardware Details:
Firmware Version: 9.108.4.p10 (0x0a096c04)
I/O Version: 0x0002
Hardware Version: 0x0012
Mac Address: 00:1d:4f:b6:7a:03
unable to open plist: No such file or directory
entering waitfor_storagedevice
entering createfilesystempartitions
AppleSynopsysOTG2::handleUSBReset
wipe entire partition: 1 (old = 300 new = 500)
creating 1048576 byte wipe buffer
524288000 bytes written in 358 seconds (1430 KiB/s)
executing /sbin/newfs_hfs
Initialized /dev/rdisk0s1 as a 500 MB HFS Plus volume
creating 1048576 byte wipe buffer
executing /sbin/newfs_hfs
Initialized /dev/rdisk0s2 as a 7244 MB HFS Plus volume
entering restore_images
executing /usr/sbin/asr
Waiting for connection attempt from server
Validating target...done
Validating source...done
Warning: the target volume may not be bootable
Erasing target device /dev/disk0s1...done
Retrieving scan information...done
Validating sizes...done
Restoring ....10....20....30....40....50....60....70....80....90....100
Copied 457511424 bytes in 138.56 seconds, 3224.54 KiB/s
Verifying ....10....20....30....40....50....60....70....80....90....100
Verified block checksum 457511424 bytes in 74.07 seconds, 6031.57 KiB/s
entering mount_filesystems
executing /sbin/fsck_hfs
** /dev/rdisk0s1
** Checking Non-journaled HFS Plus volume.
** Detected a case-sensitive catalog.
** Checking Extents Overflow file.
** Checking Catalog file.
** Checking multi-linked files.
** Checking Catalog hierarchy.
** Checking Extended Attributes file.
** Checking volume bitmap.
** Checking volume information.
** The volume Timberline5G77.N45OS appears to be OK.
executing /sbin/mount_hfs
executing /sbin/fsck_hfs
** /dev/rdisk0s2
** Checking Non-journaled HFS Plus volume.
** Detected a case-sensitive catalog.
** Checking Extents Overflow file.
** Checking Catalog file.
** Checking multi-linked files.
** Checking Catalog hierarchy.
** Checking volume bitmap.
** Checking volume information.
** The volume Data appears to be OK.
executing /sbin/mount_hfs
entering fixup_var
remove_path /mnt1/private/var
executing /bin/rm
creating directory (owner=0 mode=755) /mnt1/private/var
entering unmount_filesystems
entering clearpersistent_bootargs
executing /usr/sbin/nvram
entering update_NOR
entering img3updateNOR
img3flash_NORimage: flashing LLB data
IOConnectCallStructMethod(0) failed: 0xe00002bc
==== end of device restore output ====
2008-12-11 19:09:05.394 iTunes.exe[3108:9ec]: <Restore Device 08142208>: Restore failed (result = 6)
2008-12-11 19:09:05.394 iTunes.exe[3108:9ec]: _AMRestoreModeDeviceFinalize: 08142208
2008-12-11 19:09:07.442 iTunes.exe[3108:a1c]: WinAMRestore::OnInterfaceArrival: \\?\USB#VID05AC&PID1222#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0001#2bc4c8ef
2008-12-11 19:09:07.442 iTunes.exe[3108:a1c]: WinAMRestore::AddAppleDeviceToDeviceList: \\?\USB#VID05AC&PID1222#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0001#2bc4c8ef
2008-12-11 19:09:07.457 iTunes.exe[3108:a1c]: AppleDevice::SetNotification: CONNECT, interface type: 1, id: \\?\USB#VID05AC&PID1222#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0001#2bc4c8ef, inst: 0xaffbb90
2008-12-11 19:09:07.457 iTunes.exe[3108:a1c]: WinAMRestore::AddAppleDeviceToDeviceList, new device
2008-12-11 19:09:07.457 iTunes.exe[3108:a1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x0affb328, notify: 2, connected: 0
2008-12-11 19:09:07.457 iTunes.exe[3108:a1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x0affb6d8, notify: 2, connected: 0
2008-12-11 19:09:07.457 iTunes.exe[3108:a1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x0affbb90, notify: 1, connected: 0
2008-12-11 19:09:07.457 iTunes.exe[3108:a1c]: AppleDevice::NotifyConnect: Device type: 1, Interfaces total: 1, arrived: 1
2008-12-11 19:09:07.457 iTunes.exe[3108:a1c]: AppleDevice::NotifyConnect: DFU \\?\USB#VID05AC&PID1222#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0001#2bc4c8ef, inst: 0xaffbb90
2008-12-11 19:09:07.457 iTunes.exe[3108:b18]: iTunes: SCEP 1
2008-12-11 19:09:08.739 iTunes.exe[3108:b18]: iTunes: Restore error 6lllaass wrote:
a_monkey, wrong again.
The 1G iPod can go as far as iOS 3.1.3 that yu get here:
Purchasing iOS 3.1 Software Update for iPod touch (1st generation)
You go girl! -
Things to Know Before Building Your Mega 180
Some people have asked me for a list of tips so here is my attempt---I'll ask Wonk to sticky it if it turns out OK....
Feel free to PM me with more tips---I'll add as necessary....
TIP SHEET FOR THE MEGA 180:
So you bought that new Mega 180 and the docs leave a lot to be desired......Don't panic!! Take a look at this tip sheet. Should save you a lot of hours!
RAM AND PROCESSOR:
Several things here.....If you are going to use onboard video----you should NOT use higher RAM than PC 2700----waste of money to buy higher as the Nforce2 18G "Crush" was only designed to run no higher than with DDR333 RAM (PC2700). Nvidia warns against it on their site. I have personally experienced a LOT of problems when you try to run the onboard at DDR 400 (PC3200)----trashed Bios in most cases. Also---the 18G and to some extent---"Dual Channel" is picky about memory----try to get a matched pair of DIMMS----and if you REALLY want to be on the safe side----go to Nvidias site and look up the page that lists known, compatable memory with the NForce2 chipsetNforce2 compatable memory. I use A-Data 512 sticks---but they are hard to find.
If you are going to use a Vidcard---then higher memory is just fine----but if you are NOT planning on overclocking-----there is really NO need for higher than PC2700 as the default bus for Barton 2800+ and below is FSB 166 (DDR333---PC 2700).
Alyways run your RAM (Synch) 100%---do not play with dividers if you are using the onboard video. If you have no clue what I just said----you are fine as the defaults will take care of this----this last was for overclockers.
Processor----I like the cost of the Barton 2800+ right now----fast, cheap and even using the onboard and no overclocking----you have a fast machine that can do anything. The 2800+ also leaves the door open for a slight overclock (I have not tried this yet) without too much stress on anything.
LCD PANEL:
Do Not----I say again----Do Not use the "welcome.exe" program----or ANY other program on ANY disk or the MSI website to do ANYTHING to your front panel. That program is for the Mega 651 model and WILL TRASH YOUR LCD. The LCD panel works just fine----it doesn't need any updating.
If this advice is to late, the firmware fix is in here:
https://forum-en.msi.com/index.php?threadid=46355&sid=
Do download and install the latest version of PC Alert MSI Mega 180 Downloads----works great with the front LCD panel and displays PC info nicely.
Use the EQ mode buttons while playing in the HiFi mode----changes the sound a lot and also the display changes------COOL!
OPTICAL DRIVE:
Use an MSI optical drive----basically anything from MSI will work fine---some other drives are reported to work fine like a NEC 2500A----but if you use an MSI drive----you can't go wrong. You might want to put the drive in another machine with a floppy first----and download and update that drive to the latest firmware (most will require a floppy to do that and the Mega 180 has none.)
CABLE MANAGEMENT:
Buy a dollar pack of cable ties and go to work-----make sure ALL cables are away from the front of the intake fan for the CPU----you want a very clear path to the cooler. Less clutter---better airflow. Better airflow----lower temps.
CPU INSTALL:
Get rid of the MSI thermal grease with some Goof Off or acetone-----and get some good Arctic Silver 3, AS5 or AS Ceramique. Clean both the chip top and the bottom of the HS with denatured alcohol before applying the thermal grease. You might also want to lapp the bottom of the HS which is not very well done----but I found it not necessary. The HS/Fan unit is very easy to install----just rotate your screw down points as perscribed by the sticker on the cooler----don't tighten one screw all the way down----then go to the next.
DRIVERS:
I found the drivers on the install disk to be non-functional---- get the latest drivers from the MSI website (you can use Live Update for this) or go to http://www.nforcershq.com and get the latest Nforce2 Driver Remix from Morpheus1 or Mwarhead.
DO NOT use the Nvidia SW IDE driver (say "No" when it asks you in the driver install) Only use the ITB (In The Box) IDE driver----it's the default driver. Your Optical device will probably not function correctly (eject, etc) with the Nvidia SW IDE driver.
Nforce2 SoundStorm Drivers are a tricky topic----there are TONS of versions out there.... I've had the best luck so far with Drivers 4.31 (Off Microsoft Windows Updates---it was a Driver Update) and Audio Control Panel 4.31. Nvidia has a driver update package now JUST for audio-----posted Here
If you are having problems with Media Center III crashing----it seems to be a conflict between the SoundStorm Drivers and Media Center III, Uninstall your Nvidia audio devices in the device manager (Three of them----there is one hidden---so go to view and "show hidden devices") then reboot and let Windows rerecognize your devices and reload drivers. This will solve most problems until Media Center II has another bad crash----in which case---you may have to do this procedure over again. You can tell if it's really hosed up because the radio sound will come on automatically at boot----or you will have lost the SoundStorm Control Panel Icon in the SysTray. I'm working on different versions of SoundStorm to see which works best---will update if I find anything new. (Update)----4.31 seems to be the best but I still can'ttotally eliminate the crashing in Media Center III.
Once you get your Lan device up and running (or your modem) Go to Windows Update and make sure you are completly updated with all latest window updates---If using WinXP-----you need to be at WinXP ServPack 1a when you are done.
Use Windows Cleanup and Defrag when you are done----ESPECIALLY cleanup---to get rid of any left over temp files in the Mega----To get the BEST and most optimised defrag----run windows defrag at least three times in a row----maybe more----it will REALLY optimise the drive.
TV CARD:
The main TV Card designed for the Mega 180 is the MSI 8606-40 Mega TV Card----be careful to get it vice the other version of the MSI 8606 which is the MSI 8606-10 TV@anywhere Master.
The Mega TV Card does not include a Radio while the 8606-10 DOES include a radio. Since your Mega 180 already has a radio----you absolutely don't need or want the 8606-10 TV@anywhere Master.
Do NOT use any drivers or software you receive with the Mega TV Card MSI 8606-40----just set the disks aside. You will ONLY uses the drivers off the Mega 180 Install Disk.
The Mega TV Card MUST be installed before the menu item for "Install TV Tuner Drivers" becomes visible on the Mega 180 install disk.
Make sure your TV Card is hooked into the line called "Remote Control" within the Mega 180 itself----there is a small 3 inch connecting wire in the TV card box.
The TV and Radio function well with the remote----but you must have MSI Media Center III installed. I could not get the TV or the Radio to work without Media Center III.
Upon initial setup of the TV within Media Center III---you may have to switch the source between cable and antenna to get the initial channels to auto scan. Once done auto scanning---switch back to cable as source (assuming you have cable).
Using the remote to force the TV screen to full screen: When you use the up/down arrows on the remote----watch the menu items on the screen----the various menu item buttons will highlight as you hit the arrows.
Once you have highlighted the little arrow button on the lower right of the screen----just below the TV display (it will turn green)----hit the ENTER key
It goes to widescreen----hit the ENTER key again------it goes to fullscreen
BTW, the remote works fine-----the trick is you HAVE to have Media Center III installed and available to be called for it to control the TV Card----Radio Etc. It will start up normally when you push the TV button on the remote.
BIOS SETTINGS:
The defaults will mostly work. One thing----to get BEST performance out of the NForce 2 Onboard video----set AGP to 128 and Set Frame Buffer to 128----I had crashes with almost any other video setting. I'm still playing with PCI clock, voltages, and some other settings to get better stability-----will let you know.....
6 CHANNEL SOUND
Use all three ports in the back of the Mega 180 and then configure it using the SoundStorm Control Panel----Use the "Speaker Setup Wizard". Check and adjust using the "Test Tone" button. I'm using an inexpensive set of Analog Altec Lansing 5.1s----the sound is excellent.
That's all for now----tell me what else you've found and I'll post.
JohnMy MSI MEGA 180 has a strange display on the monitor.
I opened the boxed removed all items.
Installed the CPU (supported on the CPU compatability list for the MSI MEGA 180), installed the heatsink & fan.
Installed the HD drive.
Installed the MSI DVD+/-RW
Installed 1 DIMM module of DDR RAM PC2700 333MHZ 1GB
Pushed the Power button for the PC and the desplay is corrupted.
I tried the 4 possible configurations for Jumpers 7 and 8 to alter the FSB speed with no luck.
I also tried the 4 different J7 and J8 configurations without having the HDD and DVD-RW drives connected - same result.
I also tried the 4 different J7 and J8 configurations with the Secondary VGA output connected to my monitor.
I also tried the 4 different J7 and J8 configurations with the S-Video output connected to my TV and no signal at all.
Both my monitor and HDD work fine with my other PC.
I noticed the jumper pins are not numbered - made the configuration job a bit more tedious.
Please note the LCD screen works correctly, however the redio tuner in HiFi mode doesn't pick up any local stations.
As I am a Software Test Engineer, I am 100% confident I have checked all possible configurations including clearing the CMOS, but the system simply will not display to the VDU. The POST should at least be visible when Power is turned on for the PC mode.
NOTE: I will update the RAM Brand as soon as I find out the title from the supplier, but I believe it is OEM.
NOTE II: this is the URL to the CPU used: http://www.excaliberpc.com/product_info.php?products_id=1798
PLeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeesssss ssssssssssssssssssssssseeeeeeeeeeeeeeee eee help ease my pain!! -
Problem with hi-mode on MEGA 180
I recently purchased the MEGA 180.
I installed the driver cd and the cd that came with my msi tv tuner card. A program was installed by the tv tuner card cd that allowed me to change the welcome screen when you power on the hi-fi mode. Ever since I changed the welcome screen, the hi-mode will not work. Actually, the whole front display will not light up. I believe the program may of corrupted the firmware of the front panel? Is there a way to reload this?
Any help is much appreciated.
[email protected]I believe that application may be for the MSI 651 PC only. I would fill out the MSI support request form and see if they can send you a firmware patch to correct the problem
-
Using external LG monitor with 180 degrees rotated display
Hey everyone,
I just got a 19" widescreen LG monitor and I have it mounted upside down, so I rotated the display 180 degrees. However, when I move my mouse over links, the arrow jumps a little and is incredibly aggrivating. Has anyone seen this problem? Does anyone know how to fix it? It happens in Safari too and I already tried re-calibrating my monitor and restarting. Thanks.Me too, but my LG monitor just stopped working after I installed the recent "Thunderbolt Firmware Update".
Literally the monitor was working yesterday. This morning I installed the update and now it's broken. Great update.
Anyone have a fix? -
Im sure a lot of this ground has been covered but I thought Id put my 'want list' together. I blogged at http://www.sammorganmoore.com/fs7-notes-on-firmware/ Here is the text.. (badly formatted) The FS7 is the finest camera I have ever owned – I want to be clear on that. Slog3 is a fantastic space and the LUTs to delog it are wonderful. This makes the camera pseudo raw at 1/4 of the data rate of a raw camera.. well done Sony. Audio pots, a self powered EVF, low power consumption and other features also make the camera a wonder.. well done Sony!Now I think the camera could be moved to another level with some concentration on the firmware. I know nothing of firmware but I have a sense of what is easy to do and things that will push the processor to a place that it may not want to go. Bugs magenta shiftWell known – Custom mode kelvin dial is off presenting a magenta shift in the image as one moves away from 3200k. cache recordOn event coverage I like to use cache record , however if I engage S+Q, and shoot an offspeed clip cache record is no longer engaged when I return to normal speed. matrix unstableWhen using custom mode I like to record Slog3, Matrix Off – as matrix adds saturation that should not be there in a LOG image. Matrix appears to ‘randomly’ switch itself on. mlut unstableAn early observation but it seems like Mlut status can be lost on engagement/disengagement of S+Q general unstabilityI cant remember other examples but other settings seem to ‘randomly’ move too. For example my camera is now on shutter speed – Im sure I set it to angle – setting it to angle means less button twongling when engaging S+Q menu delaysWhen I change ISO using the HML switch the EVF only picks up the settings two seconds later – very confusing if you are used to a faster response – If lags are defined by processor speed then the EVF could display a ‘wheel or egg timer’ in the way that computers tell us ‘this is hard, bear with me’ record status lostIn S+Q one can shoot a short shot and then get the camera into a status where the camera is neither displaying the record button or the STBY status – leaving the operator at a loss if he wants to start rolling – hit the record button again or not? A side note to this is the record button on the op side is not as sensitive as most record buttons. colour balance failThis might be a function of using Slog3/Custom which does not present the system enough colour data – but often it is impossible to use the WB button. If the camera is pointed at a white card it will read ‘NG highlight’ if one stops down in 1/2 stop increments the reading then suddenly changes to “low light’ making a click WB impossible. it is called tint!Tint is called tint by everybody and even in Cat Browse. So why is it called Temp in the Sony colour menu? Simple upgrades Red dot on display offThis would be a simple warning to add.With the EX1/3 Fs100/700 one is still presented with an in monitor red icon when recording – can we have that back please. Display on/off was elegantly done with the FS100 Titles of Luts etcWith the EX1 I had many picture profiles built – they may have had titles like ‘SMM_EXT_Daylight’.. but on screen was not this title but PP3. With the FS7 the same or worse is the case. Ideally we would see something like..Recording: “EI : Slog3″Monitor: “SMM_Golden_Lut :”And in Custom Recording: “SMM_Daylight_Warm”This is super important at the moment because I have a setup “SMM_Minus17Magenta_55k” – this must be on when shooting Custom at 5500k and must NOT be on when shooting at 3200K which needs “SMM_32_Standard”(ideally this would also be burned into the meta data esp in EI so the colourist could go to the selected LUT to recreate the on set experience) Taking it furtherReally I think the complete firmware of the camera needs a complete revisit. Sony should forget their broadcast heritage menu set up and move towards offering a simple interface that aligns with both Professional Cinema cameras and professional DSLR stills cameras (1dx, nikon D4) LUTsLuts should be consistent both in playback and HFR and not kill the WFM – I will not use Mlut at all until this is the case. LUts in CustomMany shooters are desiring EI mode to be ‘upgraded’ to include sharpening NR et al. I feel this is wrong as keeping those facilities out of EI gives one a safe method of recording image. Custom mode should be expanded to offer LUTs and then one could shoot with Slog, Sharpening, NR and a LUT. SlogCustom, match SlogEIWhen Slog 3 is engaged, matrix and all colour controls (excluding temp and tint) should be turned off – so that SlogCustom matches Slog EI. ISO, Shutter Ctemp buttonsPressing the ISO button engages Auto ISO – this is wrongand can ruin shots – Sony should align ISO button to match cameras by everyone else..The ISO button should open the ISO menu, 500-1000-2000-4000-6000-8000-10000-AUTOSame for the other two base controls..Temp 3200-4000-…..1000k-AutoShutter – 360-270-180-90-45-… Auto RGB WFMThe basic way of evaluating colour in a digital camera is to evaluate large RGB histogram or WFM – addition of this.. even only to evaluate a still or in status mode would add a critical functionality – a functionality that is available on $500 and up DSLR and compact cameras. Bleeps.audio bleeps or clicks could be a confidence booters in start stop and menu navigation (EX1 FS100) AssignableEvery button shold be assignable!LUT ON/Off (see Sony PMW-F3)
A little update from this weekend. I filmed a drama short. Overall the imagery from the camera and flex of the files is absolutely performing as expected. BUT Somehow the camera managed to perform a factory reset without me noticing (possibly on battery change - maybe I didnt leave the battery in long enough after turning off?). My mind is on story, and the 20odd crew and cast I'm concentrating on. I faile to notice the factory reset - but was certainly noticing 'no synch' in my monitor! Bad lead? what has happened? Where is my WFM (on the EFV?) Rerig to lookat the EVF which the director had been watching mounted on the back of the cam (nice simple solution). Non happy director! At least the factory settings are Slog and 4k which is what I was shooting. So I lost my monitor (as 4k-1080 needs to be set up) and my WFM and also the camera went to 50p 360 shutter. So buried was I in trying to restore the monitor between takes that I failed to notice 50p/360 for about 10 takes - so they will need retiming in post. Nice images but it is super stressful to have to watch the camera like a hawk. I want the camera to by my friend not the little devil on my shoulder ruining my day whenever I take my eye off him.
-
SG300-28P - POE not correctly supported on all ports - possible firmware or hardware issue
So, I spent some time this weekend troubleshooting the issues I've had with the new SG300-28P switch and POE to many of my devices in the office. As a recap, I cannot utilize all of the 24 POE ports on the switch for POE purposes. Really only every other port [with a few odd combinations thrown in between]. In addition, the SG300-28P switch, on occasion, is sending POE to non-POE devices [e.g. my Ruckus Zone Director 1106].
Here are my POE devices [all 802.3 af-compliant]:
3 Ruckus 7982 access points
1 Pakedge access point
2 home-automation controllers
2 Polycom voip phones
I called Cisco support several times in regards to this problem, and they figured it was a hardware issue - a faulty switch. So, Cisco sent me a replacement SG300-28P, which I hooked up today. The exact problem still occurs. Default configuration [fresh out of the box]. No way I can land, for example, the 3 Ruckus 7982 AP's on ports 1, 2, and 3 [or ports 1,13, and 2]. I have to put them on ports 1, 3, and 5 in order for them to power up. In addition, I can't plug any other POE devices on the ports either between or below them. I had to skip another port bay. This is very odd behavior!! Two Cisco SG300-28P's in a row with the same problem.
However, I also had one of the new Cisco SG300-10P switches in my possession for a recent project of ours. I decided to hook up the same POE devices to this switch. ALL POE devices were recognized and worked! No need to skip a port. And it didn't matter what device was plugged in first or not. I am now convinced that it is either a hardware issue [bad power supply/transformer?] inside all of the SG300-28P switches, or a firmware issue.
Both of the SG300-28P switches were running firmware 1.1.2 [the latest on Cisco's website]. So, I decided to install an older firmware version on the SG300-28P switch that I'm returning [installed 1.1.1.8]. Here's what I found out. I could then plug 2 POE devices [e.g. two Ruckus AP's] in adjacent horizontal ports, but not three in a row. In addition, not all adjacent ports. It's funky. For example, I could plug an access point in ports 20 and 21, but not in 21 and 22. No rhyme or reason in how it worked. And I still couldn't plug an access point in adjacent vertical ports [e.g. ports 1 and 13]. BUT...
It's interesting that the same exact switch that would not initially allow 2 horizontally-adjacent POE ports to be utilized WOULD allow 2 horizontally-adjacent POE ports to be utilized when running a different firmware version. It's also interesting to note that when plugged into a "non-working" POE port, the SG300-28P would actually make a small whining noise. Very subtle noise; I could hear it when approx. 1ft away from the switch. The noise was not noticeable when ports were skipped [and POE actually worked]. Therefore, I believe that Cisco has some SG300-28P firmware bugs [at least in the last two versions of firmware] that is not truly allowing all 24 ports to utilize POE correctly. This problem does not exist with the SG300-10P switch.
I'm really interested to hear what Cisco's reply and findings on this matter would be. And would welcome a reply from one of their senior support team members/managers who could actually experiment with this, too. In addition, I'd like to know when they think a solution could be created if it's firmware-related. If hardware-related, I don't think I'll be recommending any 28P switches in our projects. Perhaps just the regular SG300-28 with a separate SG300-10P. It's a shame because the SG300-28P is more of a bargain when compared to the two separate components.show power inline
Port based power-limit mode
Unit Power Nominal Power Consumed Power Usage Threshold Traps
1 On 180 Watts 13 Watts (7%) 95 Disable
Port Powered Device State Status Priority Class
gi1 Auto On critical class0
gi2 Never Off low class0
gi3 Auto Searching critical class0
gi4 Never Off low class0
gi5 Auto On critical class0
gi6 Never Off low class0
gi7 Auto On critical class2
gi8 Auto Searching low class0
gi9 Auto Searching low class0
gi10 Auto Searching low class0
gi11 Auto Searching low class0
gi12 Never Off low class0
gi13 Never Off low class0
gi14 Never Off low class0
gi15 Never Off low class0
gi16 Never Off low class0
gi17 Never Off low class0
gi18 Never Off low class0
gi19 Never Off low class0
gi20 Auto Searching low class0
gi21 Never Off low class0
gi22 Auto Searching low class0
[0mMore: , Quit: q or CTRL+Z, One line: gi23 Auto Searching low class0
gi24 Auto Searching low class0
show power inline gigabitethernet xx (for each device plugged in)
Port Powered Device State Status Priority Class
gi1 Auto On critical class0
Power limit (for port power-limit mode): 15.400W
Port Status: Port is on - valid resistor detected
Overload Counter: 0
Short Counter: 0
Denied Counter: 0
Absent Counter: 3
Invalid Signature Counter: 17583
Port Powered Device State Status Priority Class
gi2 Never Off low class0
Power limit (for port power-limit mode): 15.400W
Port Status: Port is off - user setting
Overload Counter: 0
Short Counter: 0
Denied Counter: 0
Absent Counter: 0
Invalid Signature Counter: 0
Port Powered Device State Status Priority Class
gi3 Auto Searching critical class0
Power limit (for port power-limit mode): 15.400W
Port Status: Port is off - detection is in process
Overload Counter: 0
Short Counter: 0
Denied Counter: 0
Absent Counter: 2
Invalid Signature Counter: 1
Port Powered Device State Status Priority Class
gi4 Never Off low class0
Power limit (for port power-limit mode): 15.400W
Port Status: Port is off - user setting
Overload Counter: 0
Short Counter: 0
Denied Counter: 0
Absent Counter: 0
Invalid Signature Counter: 0
Port Powered Device State Status Priority Class
gi5 Auto On critical class0
Power limit (for port power-limit mode): 15.400W
Port Status: Port is on - valid resistor detected
Overload Counter: 0
Short Counter: 0
Denied Counter: 0
Absent Counter: 0
Invalid Signature Counter: 0
Port Powered Device State Status Priority Class
gi7 Auto On critical class2
Power limit (for port power-limit mode): 15.400W
Port Status: Port is on - valid resistor detected
Overload Counter: 0
Short Counter: 0
Denied Counter: 0
Absent Counter: 0
Invalid Signature Counter: 0
Port Powered Device State Status Priority Class
gi13 Never Off low class0
Power limit (for port power-limit mode): 15.400W
Port Status: Port is off - user setting
Overload Counter: 0
Short Counter: 0
Denied Counter: 0
Absent Counter: 1
Invalid Signature Counter: 0
Port Powered Device State Status Priority Class
gi14 Never Off low class0
Power limit (for port power-limit mode): 15.400W
Port Status: Port is off - user setting
Overload Counter: 0
Short Counter: 0
Denied Counter: 0
Absent Counter: 0
Invalid Signature Counter: 0
show interfaces advertise gigabitethernet xx (for what ports are of interest)
Port: gi9
Type: 1G-Copper
Link state: Down
Auto negotiation: Enabled
1000f 1000h 100f 100h 10f 10h
Admin Local link Advertisement yes no yes yes yes yes
Oper Local link Advertisement - - - - - -
Oper Remote link Advertisement - - - - - -
Priority Resolution - - - - - -
Port: gi10
Type: 1G-Copper
Link state: Down
Auto negotiation: Enabled
1000f 1000h 100f 100h 10f 10h
Admin Local link Advertisement yes no yes yes yes yes
Oper Local link Advertisement - - - - - -
Oper Remote link Advertisement - - - - - -
Priority Resolution - - - - - -
Port: gi11
Type: 1G-Copper
Link state: Down
Auto negotiation: Enabled
1000f 1000h 100f 100h 10f 10h
Admin Local link Advertisement yes no yes yes yes yes
Oper Local link Advertisement - - - - - -
Oper Remote link Advertisement - - - - - -
Priority Resolution - - - - - -
Port: gi21
Type: 1G-Copper
Link state: Down
Auto negotiation: Enabled
1000f 1000h 100f 100h 10f 10h
Admin Local link Advertisement yes no yes yes yes yes
Oper Local link Advertisement - - - - - -
Oper Remote link Advertisement - - - - - -
Priority Resolution - - - - - -
Port: gi22
Type: 1G-Copper
Link state: Down
Auto negotiation: Enabled
1000f 1000h 100f 100h 10f 10h
Admin Local link Advertisement yes no yes yes yes yes
Oper Local link Advertisement - - - - - -
Oper Remote link Advertisement - - - - - -
Priority Resolution - - - - - -
Port: gi23
Type: 1G-Copper
Link state: Down
Auto negotiation: Enabled
1000f 1000h 100f 100h 10f 10h
Admin Local link Advertisement yes no yes yes yes yes
Oper Local link Advertisement - - - - - -
Oper Remote link Advertisement - - - - - -
Priority Resolution - - - - - - -
Help with flashing the firmware in my optical drive!
Hi!
i wonder if anyone can help me to flash the firmware in my optical drive?
i have never done it before and i dont know how to do.
i got a NEC DV-5700B DVD-rom drive. i know it is not a MSI drive but i am going to use it for my MEGApc 180. and need to flash it to get it working as supposed. i hope.Quote
Originally posted by naw
Hi!
i wonder if anyone can help me to flash the firmware in my optical drive?
i have never done it before and i dont know how to do.
i got a NEC DV-5700B DVD-rom drive. i know it is not a MSI drive but i am going to use it for my MEGApc 180. and need to flash it to get it working as supposed. i hope.
http://forum.rpc1.org -
Help me with firmware, please!
Hi,
I have already updated my firmware for my CD-RW 48A2
But I re installed windows, so I want to know if I should re-update my firmware. I thin so, cause I do not see de 180d specification when, for example, I retrieve the drive info from Nero info tool
Should I re-update my firmware?
Please answers as soon as you can
Could you send me instructions on how to do it?
I am Spanish-spoken, so if you could answer this post in Spanish, I'd be glad. If you just can do it in English, it will be fine as well
Thanks
InesI thought so, DVD man, but the fact is that before I formatted my pc, when I used to retrieve my drive info from, let's say, the Nero Info Tool, it displayed my drive with the 180D specification between brackets.
It sayed something like that:
Recorder : Atapi CD-RW 48xMax (180D)
That 180 D specification appeared just once I updated my firmware. Befor that, the Nero Info Tool just displayed something like that:
Recorder Atapi CD-RW 48x
Well, now that I formatted my pc, I see my drive specification alike before formatting my pc and reinstalling Windows XP.
Is there any way to check whether I have the last firmware working?
Since the firmware updating required to copy some files to C:/ and then to run them from my boot disk and I haven't these files in my C: anymore (cause I have formatted my PC), I have some doubts on if the firmware updating is active or not.
Could you understand me? These are quite difficult ideas to express in English for me.
Thanks!
Pablo Muggeri
Argentina -
6D flash sync problem; flash not reporting to body? Firmware glitch? User error?
I was shooting my 6D today at the aviary. I believe I was in TV mode. Had my Canon 320EX speedlite on. I had been shooting with the flash off but turned it on. The shutter was set at 1/400th. The ISO was, I know, still set from the last room I was in, which was dark, so it is at ISO 3200.
All the birds depicted were actually whole animals; no half-birds were anywhere to be seen.
Anyway, the camera failed to reduce the shutter to the camera's max sync speed (1/180) like you expect it to do. As a result, the flash was clearly out of sync with the shutter.
Also, the metadata says "flash did not fire". But obviously it did fire.
Could this be a firmware glitch? Bad camera? Some obvious user error I am overlooking?
Scott
Canon 6D, Canon T3i, EF 70-200mm L f/2.8 IS mk2; EF 24-105 f/4 L; EF-S 17-55mm f/2.8 IS; EF 85mm f/1.8; Sigma 35mm f/1.4 "Art"; EF 1.4x extender mk. 3; 3x Phottix Mitros+ speedlites
Why do so many people say "fer-tographer"? Do they take "fertographs"?
Solved!
Go to Solution.Assuming the flash & camera are 100% compatible (newer models of bodies aren't always happy with older strobes) AND based on some problems I've had with my 1Ds2 & 580 EX it may be that the flash isn't as far forward into the hot shoe as possible, or even if it is it's not making PERFECT connections on all 5 terminals. I've had that problem a few times & now check for it. If I don't get the result I expect on my test shots (to check exposure) I wiggle & re adjust until I do get the right result.
"A skill is developed through constant practice with a passion to improve, not bought." -
I have a 180 that works fine in PC-mode, but when I try to play a record in HiFi-mode the quality of the sound gets really bad such as short interruptions of the songs.
Also, when using Deluxe Center III, I cannot enter the "music" category or the system freezes. I see the text "Loading..." in green in the top left corner when this happens.
I have AMD XP3000+ as well as LITEON 8X DVD+-R/+-RW that has Pentium III b450MHz or higher as a system requirement.
I´m sort of a newbie when it comes to hardware, so any help would be very appreciated. Does it have to be a hardware problem when the computer is in HiFi-mode, as the of the computer is powerless?I have the same thing happenig on my MSI DR8-A2, not in the same way since i dont have a Mega machine (Yet) but the same idea applies. Often it turns out that the disk doesn’t always load first time and you are forced to eject, and reload the disk. Check your CD drive in my computer when you put in the disk to see if it recognises it. When it does, try loading it in the program again. It may reoccur in the other DR8, and the DR12-A but I can’t say for sure. It may occur on the other MSI drive models, as they properly use the same base firmware. Your Drive may also share this problem.
Maybe you are looking for
-
Exporting my SWF from my FLV movie but it doesnt play! Help
Hi All, Ok im a real beginner here and need some of your expert help. This is the deal. Im working between Dreamweaver & Flash cs4 Now i have a FLV video clip that i want play on a webpage with a full screen option so this is what im doing: File > Im
-
Qosmio X300-130: Problems with some drivers in windows 7 64 bit.
I have installed normally in my laptop windows 7 64 bit version. Before I continue with my main problems I am in the forum for answers and I found this [post |http://forums.computers.toshiba-europe.com/forums/thread.jspa?messageID=232906𸷊] . H
-
How would I get information out of a Cdata tag?
Read in CDATA[] based information? I can never find out how to access the data inside of Cdata. Any one got any ideas? we never covered this in school and google just confuses me. So how do you get all the data out of Cdata to do what ever with it? t
-
Trying to retrieve the editValue of a list box selection with multiple selections
I have a requirement to display the text and the value of a multiple choice list box but as soon as there are multiple selections the value displayed is the rawValue. My code is something like this: verifSubTaskDescID.addItem(this.editValue); verifSu
-
Udev not loading the right driver for usbtmc device
I have a usb beam profiler and I'm trying to get it to work on arch linux. It works using NI-VISA, so I should be able to communicate with it using usbtmc. However, when I plug it in, it does not show up in /dev. I think the problem is that udev is