error! install unsuccessful

[Charvelguy]

"Riffworks cannot find its graphic resources"
please uninstall and try install again..(or to that effect)

In my opinion, the Line 6 update has issues! or I do! (I definitely do now)
I am a little bit at a loss. This update doesn't even show on Line 6 servers.
When I run Monkey, it shows the latest update available is 2.10.0, same as what is shown on the Line 6 website. Any idea when the 2.11 update is going to show up on the Line 6 site?

So, I ran the update and now...I'm in a loop. I had shown build 2710 in program listings and I was using build 2710 rather successfully. I had been able to install and run 2810 but it didn't stick around long (why?--don't ya just love it when that is put out there? but it is curious, multi install attempts in conflict?)

When I went to save my songs on the new build. On one song in particular I got a bunch of errors. So I saved a dump file and rebooted to load, recover and save the song file.
Its been rather goofy since as everytime I have ran 2.0, especially with the yet uncorrupted version of this song it has ended in error.
I'm also now getting 'invalid file' when trying to load the lastest version of my song.
Somehow.. I cannot help but think it is a bug relating to the VST7 that has been a problem off and on all summer.

When I ran Monkey, it also showed the build as 2.10.0a yet, the latest build available according to Monkey IS 2.10.0.
Everytime I load up Riffworks it wants to run the updater.

Riffworks 2.0 build 2710 HAD showed previously installed in windows 'add and remove' programs. I have the icons and programs still showing for 1.0 and 1.1 in my program list and Riffworks 2.0 previously showed the 2710 build in the populated list under those. That was replaced by line 6 2.1.1 vers showing the monkey icon.

Following this so far?

Windows now doesn't even show Riffworks 2.10 as a listed program to add and remove. It does show Riffworks with a monkey icon, but the brown pick version is now gone.

Ok, so up to this point, I still have a workable version of 2.0 that is acting buggy.

RW update says to uninstall the 2810 build update and start over with a reinstall.
I went into programs and did that, found the Riffworks with the monkey 2.11 build and ran the uninstall.
Now I no longer have ANY 2.0 version build..it completely uninstalled the 2710 build and the 2810 build.

Fortunately, I believe I saved both program files but its not a big problem.

I now have folders for Riffworks under several locations over 2 partitions because I previously installed RW under a LINE6 folder, not Sonoma. I have a good idea where it needs to go, back under the LINE6 program folder, but it seems somewhat a mess and now I have no working version of 2.0 on this system. I guess I'll have to reinstall.
The question is, do I need to install 2.10 again in order to run a sucessful update because the update itself is not the full version?

I have to check my other build and see if it is having similar conflicts.

Ideas? (I'm now off to send an email with the dmp files btw)

[davenz]

That resource error occurs when the update is installed into a different directory than the original install. The updater doesn't pick Riffworks current installation path from the registry like some updaters - it is hard-coded to c:Program filessonomawireworksriffworks (or whatever) so if you installed Riffworks into a non-default location this is what happens when you just click next, next on the updater. Uninstall it all and reinstall the original and the update into the same directory and that should solve that problem.

Edit: Just reading your post further it would appear that you have installed an updater not designed for the version you have (if I read it correctly) which would cause all sorts of issues. Uninstall the whole lot and reinstall as suggested above. If you have the Line 6 version, to my knowledge there is no update for it yet to the latest version, so resist grabbing updates unless they are specifically asked for by Riffworks when it starts up.

Then again, I might have gotten the whole thing bleeped up anyway!

Dave.

[Charvelguy]

Thanks for your reply.
I believe that partly is the issue. I'll have to remove all the extra folders and reinstall everything either to default or to the correct location, cause I obviously missed the correct target the first time or two and that now has probably caused further conflicts..

This is the updater it is prompting me with, so that is the one I'm using. It is likely the correct one as the Sonoma update went out few days in advance (18th?) and this one came up on the 24th.

So, I just checked my other build and everything is looking ok on that system. I'm pretty sure I do not have Riffworks loaded to the default folder (its on the F partition but in a Sonoma folder) on that system but it appears to have taken ok so far w/o issues.
I think its safe to say, you can change the drive partition, but not the program folder?
So I think the issue on my older build is I stored it to Line6 folder (as I downloaded 2.10.0 off Line 6 website as it is a line 6 version) I either renamed the program folder or it was orginally set to go to C:program filesLine 6.
The sonoma update is wanting to go to a sonoma folder and that is creating the conflict if it is hard coded as you say.

If you are a little confused about my talk of builds, I have two desktop systems with RW installed. I was planning on using one converted and one with an unconverted version initally.
It looks as though I'll likely convert on all my systems as the benefits are greater and less restrictive.

I have two systems to update, an older and a newer (plus a laptop-I haven't gotten to that)
The newest system build seems to have taken the update ok and Monkey shows the RW build as 2.11.0a.

I have stated 2.10.0a showing as the Rw2 update version in my previous rant which is about a problem with my older build. Since Rw2.0 is no longer on that system, I do not know for certain if that was correct as it shows nothing under present install but it may have said 2.11.0a..altho I know the update did take (as I checked after install and reboot) and then it seemed to just vanish on the first build. It kept wanting to run 2810 update on the somewhat existsing 2710 build.

Something got in conflict, probably a code issue to folder as you state. This is probably going to have some registry issues now also to cleanup.
In fact, it may be registry issues that are going on as well that are at the heart of this.

[Charvelguy]

The newest system build shows the program list populated with the 2.11 update and it shows the brown pick icon next to the listed program, which is how it should be.

It was not like that on my older system build, ..that showed the monkey icon.
I wish I would have taken screenshots.

[Charvelguy]

What is strange is my main PC shows build 2710 as an installed program when I do a search. (with the brown pick) It does run and function as a standalone app but this build won't connect to the Sonoma servers with my Key. Its not appearing in the populated program listings as one to add or remove.
So, its still installed but Windows no longer recognizes it as such. It does show up as a running app in software explorer when opened. ID's as RELEASE 1300 and as not digitally signed.

[dug]

Hi Charvelguy,

Not sure from your last message if you have everything working or not. Please let me know. Try not to use "this build" or "it" so that I can keep what's what straight. Example: 2710 shows as an installed program. 2801 does not.

BTW, that's a bummer that the updater did not detect the file being in a non-standard location. I'll look into that. I thought we were using the registry to find the location.

thanks!
dug

[Charvelguy]

Hi Dug, my apologies about the terminology use confusion. I realize I (and am still) weaving my way in using 'this build' in reference to both the RW software and my pc's.

The problem isn't solved on my main pc, which is a Dell mini tower.

Another odd thing is ... RW build 2810 is showing up as a runable prgram when I do a search into the bowels of my PC. I can go into a folder, click on the brown pick and run the app as a standalone.

I'm sure I can get it figured out but it seems related my driver loading problems I encountered earlier in the year. In the meantime, I'm transferring everything over to another PC and hard drive.

Thanks for your reply and attention to the matter.

[davenz]

BTW, that's a bummer that the updater did not detect the file being in a non-standard location. I'll look into that. I thought we were using the registry to find the location.

thanks!
dug

Dug,

I thought I mentioned this a few eeks ago; mind you, that might have been an 'inside thought' that didn't make it outside. My install location is not default and every update I have to point it in the right direction. Also, the updater blows away any custom 'default' riffs we may have created - why? Is there some code in it that might prevent Riffworks from playing should the .exe change so the default riff is changed just in case? The only reason I ask is that I create a new default riff and keep forgetting until the upgrade progress dialogue is half way across. Easily enough created again but it seems a little odd to replace that every time an update comes through.

Cheers.

Dave.