Jump to content

Roxio Community

Repair Process


  • Please log in to reply
1 reply to this topic

#1 sknis

sknis

    Digital Guru

  • Digital Guru
  • PipPipPipPipPipPip
  • 22,941 posts
  • Gender:Male

Posted 15 March 2007 - 03:53 AM

I just tried to open Media Ticker 2 and found that something that I've added to my computer may have created a conflict since the program would not open hang.  I had added Buzz, Photoshop 5 and Photoshop Elements 3 recently so I don't know if one of those had anything to do with the program not opening or if it was some other hiccup.

I used Windows add or remove programs process to select "Modify" the program.  That gave me about a half second non-repair.  It still wouldn't open.   When I used the "Click here for support information", I got the option to repair from there.  That option worked, I saw the program reinstalling and when I rebooted, it worked  as desired.

I don't know if that is a Windows issue or if that is something in the Roxio installer that doesn't call the correct repair routine.

BTW, I looked at the events log but it didn't provide much information on the hang.
Regardless of what I say about computer maintenance, there is no need to defrag a solid state hard drive.

PC  Windows 7 Ultimate 64bit  
Velocity Micro ProMagix ©HD 60; evga x58 motherboard, Intel i7 @2.93, 12G RAM, EVGA Nvidia 560TI superclocked video card, SoundBlaster X-Fi Xtreme audio card, Buffalo external blu-ray burner; Creator 2012. PhotoShow 6, VHS to DVD 3Plus.

Laptop - Windows 7 Home
Dell XPS 1645, Intel I7 1,6G with overdrive ,4G RAM, 1 GB ATI Mobility Radeon HD 5730, Sound Blaster X-Fi MB Panzer, 500G hard drive.

Apple =OSX 10.5
MacBook Pro; 15.4-inch widescreen display, 2.4GHz Intel Core 2 Duo, 2GB memory, 200GB hard drive, 8x SuperDrive (DVD±R DL/DVD±RW/CD-RW), NVIDIA GeForce 8600M GT with 256MB of GDDR3 memory.  ILife 08, Toast 10, Final Cut Express 4 and Photoshop 4.

#2 Juan

Juan

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 15 March 2007 - 07:48 AM

Thanks for the report.  We did have a problem with a previous build of Buzz, where the installer was overwriting a component shared with MediaTicker.  As you discovered, re-installing MediaTicker puts the right component back in place and fixes the problem.  The latest build of Buzz should behave well.




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users