Windows XP + Safe Mode = UMC1

[drummerdano1973]

I havent fully put it through the paces yet but I did what Vincent at EMO told me to do if I'm running Windows XP. He suggested trying to do the FW update in safe mode (F8 on startup). So I just did. No hang ups etc on the upload like before.

Will watch some Dish Sat and PS3 Blurays and report back if the problems were solved doing it in safe mode........i.e. Dropouts, popping, bass and treble, PLII etc etc.........

Being a snobby Mac user this is all the more reason to despise windows if its the cause of the quirks in the upload!! ;D

[kumayama]

At Vince's suggestion, I did this very thing TWICE this afternoon. There are actually more problems now than after I had run V6 without safe mode.

I spent literally hours to get V5 installed, now I have hours into multiple (5) installs of V6, and I'm still stuck with much the same issues as when I first got the unit. I'm now just thoroughly discouraged.

[drummerdano1973]

I'm there with you man!! Why are we the ones having to figure this stuff out. I am avoiding sending the unit back but at this point it looks like I have no choice. I have spoken with EMO 3 times regarding this and still have not been able to get the UMC to work "right".

[satman24122]

Ha Guys I am having the same trouble and have use Windows XP and Window 7 and my unit keep rebooting in the middle of the update or just turns on and off every 2 or 3 seconds. I also tried save mode different cable and still no luck. Do you know if there is a way to do a factory default from the box?

[2infinity]

I will share my experiences on this matter. I installed V6 using XP not in safemode Two Days Ago. I tried the safeboot mode in attempts to fix the DD dropouts today.

I am running a macbook that can dual boot (via bootcamp) Windows XP & MacOS.

First, if anyone wants to try the safemode install on bootcamp, here is what you have to do:

1.) Go into MacOs and switch the startup disk to your windows partition.
2.) Reboot holding down F8
*Be prepared as you will need a USB keyboard & Mouse each plugged directly into the CPU's USB ports*
3.) Windows will boot into its black screen and ask what mode you would like to boot into.
4.) Choose safe mode sans other options (e.g. networking)
5.) Follow the steps provided by Emotiva in the update

Second let me note a few parts about the update.
1.) Installing the DSP flash went well!
2.) At the end of step eight, bullet point (J.) states that
"Press the front power button once to turn the UMC1 on. It will begin to boot up and then do a reset. "

I wasn't sure whether this means that the UMC-1 is supposed to boot up, then reset itself or if we, as the user were supposed to do another factory default as outlined earlier in step (4.)

I spoke with a tech at Emo who said it meant to do a factory default. So I did a Factory Default

3.) I went through step (9.) in a fairly straightfoward manner. However, when I got to bullet (L.) under step (9.) which states "The unit will cycle this loading message in the display several times. " It only loaded once.
4.) Bullet (M.) states "The unit will then momentarily shut down and power back up on its own." However mine just stayed on from the last power up. I did a factory default again and then moved onto reprogramming the UMC-1

OK so observations. I played with it for an hour or so. It seemed to do ok and I was thinking that the safemode had fixed my problems.

Unfortunately, while watching a TV series on DVD in DD, I lost the center several times in 10 minutes and also lost all 5 channels during that time as well. It should be noted that the sub channel remained though. Also, I could be imagining things, but it seems as if the sub is a bit loud or not crossed over correctly. I don't have the software to verify this though.

I will admit, in my limited testing, I had to use FF and RW to cause these problems. But still, they should not persist.

It could certainly be user error in updating, but I followed the directions to a T. I have noticed since doing it this way that lock on times for DD and other signals are really fast!

That being said, The steps that I noted where things did not go as described might be an artifact of the "reset" vs "load default" descriptions in the instructions under Step (8.) bullet (J.)

So I am going to call tomorrow and just be sure that isn't anything else I could do. Might send it back for them to do the FW.

So anyone out there using XP that has got it to not give the DD drop?

[snodog]

Well Lonnie did say that the Cirrus chip was responsible for the dropouts so if that is the case, why aren't they responsible for a remedy then? It has to be happening with others using the same chip, hate to say it but maybe that is as good as it will get...hopefully not. Mine dropped out only once so far in the last two days via cable motorola box, however I also am using digital optical cable and not HDMI.

[RSavage]

Apr 15, 2010 23:43:33 GMT -5 @snodog said:

Well Lonnie did say that the Cirrus chip was responsible for the dropouts so if that is the case, why aren't they responsible for a remedy then?

I'm old and stuck with the term 'dropouts' meaning transient little events that used to happen with audio tape. What is happening with my UMC isn't a 'dropout'...it's the complete or partial LOSS OF AUDIO when changing channels or using FF or REW. It can also manifest itself as the complete loss of one or more audio channels. These events are not transient...they are steady state and will not resolve spontaneously.

I don't think this is what Lonnie was attributing to Cirrus. If it IS, then we have big trouble.

R

[ratmice]

Apr 16, 2010 0:00:15 GMT -5 RSavage said:

Apr 15, 2010 23:43:33 GMT -5 @snodog said:

Well Lonnie did say that the Cirrus chip was responsible for the dropouts so if that is the case, why aren't they responsible for a remedy then?

I'm old and stuck with the term 'dropouts' meaning transient little events that used to happen with audio tape. What is happening with my UMC isn't a 'dropout'...it's the complete or partial LOSS OF AUDIO when changing channels or using FF or REW. It can also manifest itself as the complete loss of one or more audio channels. These events are not transient...they are steady state and will not resolve spontaneously.

I don't think this is what Lonnie was attributing to Cirrus. If it IS, then we have big trouble.

R

I agree with RSavage, these are not dropouts (transient) these are loss of audio (permanent).

Guess I'll have to try an install using safe mode. Third times the charm, right?

[ICBM99]

Yep I agree not "dropouts" as RS explained them, but complete loss of audio. Should we coin a new term??

how about Nuked ;D

[ratmice]

I just spoke with Vince. He stated, in no uncertain terms, that, if you are using XP, you have to use safe mode + networking to update. Any other way leads to the posssibility of corruption. He did not say that there would be any outward manifestation (read observable errrs) of the corruption. Now where I come from networking has nothing to do with USB, but he stated it (USB) would not transfer data without the networking option. So there ya go.

[jklow888]

Apr 16, 2010 14:51:18 GMT -5 ratmice said:

I just spoke with Vince. He stated, in no uncertain terms, that, if you are using XP, you have to use safe mode + networking to update. Any other way leads to the posssibility of corruption. He did not say that there would be any outward manifestation (read observable errrs) of the corruption. Now where I come from networking has nothing to do with USB, but he stated it (USB) would not transfer data without the networking option. So there ya go.

Strange - I did the upgrade in Safe Mode with no networking last night. Followed the steps exactly and also got the issue in step 9 like 2infinity. I did a hard reset and it worked ok. FF/REW for 30 mins of content on a Tivo did not result in loss of audio as before and the audio lock-on is faster (almost instantaneous) when coming out of FF/REW.

Switching tuners with the "Live TV" option resulted in no audio (what ctbarker32 described in his thread "New Firmware - Weekend testing suggestions"). I had to force a channel change on that tuner I switched to and it got audio, then changing back to the other tuner had audio. I need to retest to see if the DD 3/2 to DD 2.0 changes is the cause when ad-breaks come up.

I will add - during the upgrade, when doing the File Open part, it took ages to list the drives/folders but did eventually list them and allow me to select the relevant file to upload/upgrade.

[mditty]

I'm wondering if the problem isn't XP vs vista vs safe mode but instead the speed of the system causing some timing issues on the firmware load. XP + safe mode would optimize the system for speed and allow it to work. Win 7 is normally run on multi-core fast machines so it would also load faster.

Mac with emulator would run quite slow and be less likely to work than no vm running dual boot.

[shinsho]

Ok... I thought I would post here and share my experience with a re-install of V6 using the XP in safe mode method.

First I should state that my original V6 flash was done using an old Windows XP laptop and it installed the firmware first time with no issues. At first I assumed everything went fine as I put it through its paces over the next 48hrs. Yesterday while watching a few shows off of my DirectTv DVR I noticed the Dolby Digital problem. In the switch between DD 3/2 and DD 2.0 I would experience the loss of some or all channels as has been reported here by many.

Today after reading Ratmice's posts about Emotiva suggesting the safe mode install when using XP.... so I decided what the heck and followed the instructions to a T except in Safe Mode + Networking.

My results after 2 hours of "watching" programming off of my dvr and live Tv of various channels is I believe this has fixed my Dolby Digital problem!!! Now I have spent 2 hours fast forwarding , pausing, changing channels and actually watching the commercials looking for the speaker channel drop out I was experiencing before and I have had none of them, yesterday I would get about 4 or 5 drop outs per hour depending on how many times I paused or fast forwarded. Also Like JKlow888 I am experiencing near instantaneous audio lock on after pause and fast forward.

So to surmise .... I would say if you are getting a few of the glitches that others are noting , it may be worth it to try a re-flash using Safe Mode. YMMV

[RSavage]

Apr 16, 2010 19:02:19 GMT -5 @mditty said:

I'm wondering if the problem isn't XP vs vista vs safe mode but instead the speed of the system causing some timing issues on the firmware load. XP + safe mode would optimize the system for speed and allow it to work. Win 7 is normally run on multi-core fast machines so it would also load faster.

I'm guessing most modern machines are capable of crunching more data than the USB bus can pass....unless there is some HUGE overhead built into the updater....which is doubtful given the apearant lack of error checking. But then again, I would have expected 'corruption' to cause random problems, so what do I know

R

[mditty]

Apr 16, 2010 19:18:20 GMT -5 RSavage said:

I'm guessing most modern machines are capable of crunching more data than the USB bus can pass....unless there is some HUGE overhead built into the updater....which is doubtful given the apearant lack of error checking. But then again, I would have expected 'corruption' to cause random problems, so what do I know

R

Agreed, any system should be able to handle the USB processing. I'm more saying it could be some race condition, which might be affected by cpu speed.

Main point was the problems might be tied to the hardware XP vs Win 7 runs on than just the OS.

[dkjohn]

Are you kidding me first all of the problems with the first firmware upgrade and then they come out with the second upgrade and the same combersome system to upgrade everybody does the upgrade now they say it only works fully if you run in safe mode this is getting comical but I am p#$%ed off for real after the second install nothing has changed for me.

[BillBauman]

Apr 16, 2010 19:31:21 GMT -5 @mditty said:

Apr 16, 2010 19:18:20 GMT -5 RSavage said:

I'm guessing most modern machines are capable of crunching more data than the USB bus can pass....unless there is some HUGE overhead built into the updater....which is doubtful given the apearant lack of error checking. But then again, I would have expected 'corruption' to cause random problems, so what do I know

R

Agreed, any system should be able to handle the USB processing. I'm more saying it could be some race condition, which might be affected by cpu speed.

Main point was the problems might be tied to the hardware XP vs Win 7 runs on than just the OS.

Safe Mode is actually slower than "regular" mode. What it provides is a stable environment from which to load timing-sensitive code during the update process. There are a significant number of background processes set to a higher priority than foreground programs in a Windows XP system that will be given preemptive priority of system resources even if they are not doing anything during the update. Many of these processes are not running during Safe Mode, and this is probably making a much more stable final code load on the UMC-1.

As Vista and Windows 7 are completely different architectures (in many ways) from the now-dated XP architecture, they will better behave when a user-mode foreground process appears to be using or would benefit from using the majority of all system resources.

[Chris]

Apr 16, 2010 19:13:08 GMT -5 shinsho said:

So to surmise .... I would say if you are getting a few of the glitches that others are noting , it may be worth it to try a re-flash using Safe Mode. YMMV

Thanks for the update. I still don't think this is the solution. The fact you haven't had an audio glitch is not a function of time but a function of having the right sequence of events occur to cause the audio dropout.

Tonight I watched a full hour of ABC HD without one audio dropout. I then changed the channel to SyFy HD and within eight minutes I had an audio dropout exactly as predicted during a commercial break when going from DD 3/2+LFE to DD 2/0 to DD 3/2+LFE. Right now I can pretty much predict when this will occur which exactly defines the definition of a bug to me. I can't explain the cause but it's there.

May I suggest you continue to test and observe now that we know what we are looking for. The sooner we can get confirmation of this bug the sooner we can stop talking about firmware corruption and actually get on with a fix to the problem.

Just a last idea on the firmware integrity. Can't a utility be written by Silabs or someone that can do a checksum check of the code that is loaded into an existing flashed UMC-1 chip? If code can be uploaded, it should be able to be downloaded and compared with a checksum. Couldn't this finally put an end to the endless corruption discussions. If Emotiva can prove to me in a way such as I describe that the code is indeed corrupted then I guess I'll have to eat my USB cable! Otherwise, I'd rather we get on with the business of fixing bugs.

-CB

[RSavage]

Apr 16, 2010 20:55:24 GMT -5 Chris said:

Just a last idea on the firmware integrity. Can't a utility be written by Silabs or someone that can do a checksum check of the code that is loaded into an existing flashed UMC-1 chip? If code can be uploaded, it should be able to be downloaded and compared with a checksum. Couldn't this finally put an end to the endless corruption discussions. If Emotiva can prove to me in a way such as I describe that the code is indeed corrupted then I guess I'll have to eat my USB cable! Otherwise, I'd rather we get on with the business of fixing bugs.

;D

[roadrunner]

Apr 16, 2010 19:59:21 GMT -5 dkjohn said:

Are you kidding me first all of the problems with the first firmware upgrade and then they come out with the second upgrade and the same combersome system to upgrade everybody does the upgrade now they say it only works fully if you run in safe mode this is getting comical but I am p#$%ed off for real after the second install nothing has changed for me.

DKJohn and other upgraders having problems,

I am mildly surprised that Emotiva's Step-by-Step Instructions did not advise everyone to make sure their pc was in "safe" mode before starting the upgrade. During the last software upgrade, several Lounge Member, including me, warned users that they should either shut down all extraneous software or reboot to safe mode. Nearly every complex piece of software you install these days advise that you disable all virus checkers, firewalls, gateways, chat programs, etc before attempting to install the new software.

I thought after all the problems people went through attempting the last upgrade that they would automatically reboot into safe mode to install this FW. Apparently, not enough people saw the various advice posts during the last round of upgades. Windows is a very "sloopy housekeeper" and cannot be trusted to properly handle new installs without takiing the necessary precautions. This has long been the case with installing software on Windows based PCs.

Please take these precautions in all future attempts to install the FW on your UMC-1 -- whether or not Emotiva's check list includes this warning. It will save you time and lots of headaches. ;D