Cameyo

Members Login
Username 
 
Password 
    Remember Me  
cameyo -> Cameyo usage -> Package Editor not working - anymore
Post Info TOPIC: Package Editor not working - anymore
hiro


Member

Status: Offline
Posts: 5
Date:
Package Editor not working - anymore
Permalink   
 

Hi

I post my "Package EDITOR" problem here, hoping it's the right section, as my Cameyo packages (results) themselves all work fine.



Under Windows 10 64-bit:

Cameyo 3.1.1443 "PACKAGE EDITOR" won't launch — anymore,

while Cameyo itself still works perfectly + knowing that "Package Editor" USED TO work with no problem at all.

I tried Cameyo 2.6.1220 "Package Editor": same result.



So, Cameyo 2.x & 3.x still work as expected. But I (of course) want to edit the created packages. As soon as I click the "Edit package" option, all I get is:

—— a small blank window, with no message; only a white cross on a red circle + OK button. And then another blank window: yellow triangle +  exclamation point + OK button. ——



Since it used to work — I edited several / various Cameyo packages —, and since it works in another machine, under Windows 10 32-bit, what could the problem be?



Those BLANK windows sure don't help: I just cannot figure what is or could be missing, in my Win. 10 64-bit PC. A ".dll" file in my system? Or corrupted (but I don't know which system ".dll" files Cameyo requires)?

A registry key / value? One of Windows 10 "services" or other component(s)?

I tried to set (free all) "permissions" on Cameyo.exe + its "VOS" folder (in "Roaming"). I also tried the cleaning command line: cameyo.exe -remove (which worked). And of course: deleted the "VOS" folder. And all possible compatibility + administrator modes. But still no change...


And could not find any hint or help among — kilometers of — guides, advice & forums I've read so far.



Now, if those two blank windows display, it means they've been programmed to do so (smile) — within Cameyo.exe and/or its "VOS" folder, I guess.

Unless they are "Windows 10" system warnings instead of Cameyo built-in components, could anyone please tell me what they mean?

And above all, how to fix "Package Editor".



If possible, I'd rather keep avoiding "virtual machine" apps, as I encountered problems with those, and since "Package Editor" DID work fine without the help of any "VM".

Thanks very much in advance.




-- Edited by hiro on Sunday 20th of November 2016 03:40:24 PM



-- Edited by hiro on Sunday 20th of November 2016 03:52:26 PM

Attachments
__________________
mule


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

Please try Cameyo.exe -Remove again.  After receiving successful message, delete registry keys HKCU\SOFTWARE\Cameyo and HKCU\SOFTWARE\Cameyo Package Editor.  Do the same for HKLM if they exist there.

If you still receive error, please advise version and build of Win10 x64, e.g. Version 1607 Build 14393.447.



__________________
hiro


Member

Status: Offline
Posts: 5
Date:
Permalink   
 

Hi,

1. thanks for the quick reply.


Cameyo.exe -Remove done again (displays "removed successfully").

HKCU\SOFTWARE\Cameyo
and 
HKCU\SOFTWARE\Cameyo Package Editor
+
HKLM

do not exist as I cleaned them all; so nothing to delete from registry anymore (I double checked, though).


——— Then, new test yields the same error : 2 blank windows & no "Package Editor" launch, still... Although I now SUSPECT (?) them to be Windows 10 components, instead of "Cameyo" built-in annoyances.


Windows ed.: 10 x64 professional
version: 1511
OS version: 10586.679

(I do NOT want the "Anniversary" upgrade...).


—— Please note : "Package Editor" worked just fine a few days ago.


— Attached (if any help?): "CameyoTracer" log. *, obtained by starting "Cameyo" (always OK) and then trying to launch "Package Editor" again.


Thanks a lot for your help.


* OK, images only, here... So, uploaded to:

http://s000.tinyupload.com/?file_id=98348437178554822835

and click light green file name "CameyoTracer-debug_LOG__on-Cameyo-3.1.1443-Package-Edit-failure.txt".

 

 

 



-- Edited by hiro on Monday 21st of November 2016 09:24:50 AM



-- Edited by hiro on Monday 21st of November 2016 09:26:19 AM



-- Edited by hiro on Monday 21st of November 2016 09:29:53 AM

__________________
mule


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

Have there been any recent changes to your .NET or your userprofile?  Package Editor uses .NET.  Your log shows your profile name as "_"



__________________
hiro


Member

Status: Offline
Posts: 5
Date:
Permalink   
 

I wish I was able to detect or trace any changes in my ".NET";  I've (also) been wondering about that.

My (weird) "_" user name is just the one I chose when I installed that PC. So no change occurred there.


As I couldn't find this info. by myself : which ".Net" version does "(Cameyo 3.1.1443) Package Editor" require, please?

______________________


I used to run Cameyo 2.0.890 in Win. XP SP2 machines (c. 2014), with no ".Net FrameWork" installed. = Reason why I didn't suspect that in the 1st place...

OK, I've read : "EDITING packages = only from version 2.x on" (can't remember which one precisely; anyway, that's why I tried "Cameyo 2.6.1220" — with same result : error on "Editor" launch).


Something — but what? — must or may have changed in ".Net FrameWork", though. Therefore (+ so far), I downloaded "NetFxRepairTool.exe", which didn't fix anything, as it reported no ".Net" problem...

 

 

[edit]   I just tried to enable or re-enable (not knowing if it was enabled when "Package Editor" worked OK): ".Net 3.5, which includes .Net 2", in Windows 10 settings... What an "experience"!:

after a few "BSODs" (!) + my screen blinking completely, until I HAD to restart using the main power button (!)... two more "BSODs", and Windows FINALLY accepted to load normally again.

And... "(Cameyo) Package Editor": STILL won't start (of course, after using "-remove" + cleaning the registry again).

As you can tell, I REALLY want "Package Editor" to work...

______________________


In addition : should I manually download + install any partial Windows 10 update, I would. But, if so, which one, among those tons of "KBxxx"*?

* NOT the big "Anniversary" one / thanks...

... that happened to install BY ITSELF (darn!) in another PC — that runs "Package Editor Cameyo 3.1.1443" OK :

Win. 10 pro. 32-bit, ed. 1607, OS version 14393.447

______________________


——— Also, I just tried... this, to check on a possible ".Net" issue:

— BUT, even if it worked (& it does NOT), I don't want it, since it's not freeware (very limited free version) :

"Evalaze Free 2.2.1.1". That one won't even start AT ALL : same two blank windows!..



Thank you.




-- Edited by hiro on Tuesday 22nd of November 2016 06:30:59 AM

__________________
mule


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

It definitely seems as if something is corrupt with .NET.  XP did not ship with .NET installed, so if there is none present, Cameyo Package Editor will give a message that .NET 2.0 framework was not found and it is starting simplified, basic Package Editor.  Evalaze gives an error on XP with no .NET installed.  Win7 shipped with .NET 3.5, so Package Editor should start with no problem.  Win8-10 come with .NET 4 and 4.5, and again, full Package Editor should start.

I would guess that your corruption is with .NET 4, 4.5, or 4.6.  I hope you are able to fix the problem.  Good luck!

 



__________________
hiro


Member

Status: Offline
Posts: 5
Date:
Permalink   
 

Thank you. Yes, it sure seems like some .Net corruption. So far, I've not been able to fix it. "Net Repair Tool" didn't help a bit either.

I tried several other checks, cleanings, files replacements (sometimes refused), etc. The problem... remains a (tough) mystery !

Only thing left to do: restore the whole partition – as I made a backup (but not possible right now);

– although restoring won't tell me what's or was wrong. Should it happen again, I would have liked to understand what to modify... especially since the cause is probably tiny, as nothing else went wrong (apparently).

So for now: virtualize in this PC, then transfer results to the other (Win. 10 32-bit) one, to edit packages... At least, that works.



.

__________________
hiro


Member

Status: Offline
Posts: 5
Date:
Permalink   
 

smileK: at LAAAST! "Package Editor" is working: again! smile

Drove me nuts...

So: is daydreaming allowed, here? Yes? Good! Then I sure wish that some next version will NOT depend on ".Net Framework" anymore. May be in another life, huh?..


I don't know if this (below) might be of any help to anybody. I don't even know precisely enough WHICH one, among the changes I made, fixed the problem... Anyway, here's what I tried:


1. Downloaded + installed ".Net 4.6.2", hoping it would fill some "gap" (missing file(s) or corrupted). But "Package Editor" still wouldn't start...

2. UNinstalled ".Net 1.1" (was there because required by some old app) — and should have tested right away, but didn't (...) & jumped to: 

3. In Win. 10 built-in components settings: UNinstalled by UNchecking: option ".NET Framework 3.5 (includes .Net 2.0 & 3.0)"

– while leaving ".NET Framework 4.6 Advanced Services" in place + as is (black = some services enabled only), of course.


Now, I know what next problem to expect: due to quite a few programmers' usual mistake, some (aging) apps will refuse to install &/or work,

as they include checking if the expected ".Net" version is actually installed. Mistake: because newer versions of ".Net" are supposed to include former versions. That's what I've read, anyway.

Since I'm using some old apps, I will HAVE to reinstall either ".Net 1.1" or "2.x" or "3.x": temporarily — & will THEN roll back again, in order to let "Package Editor" start...


The conclusion COULD be (though I wouldn't bet!): "Package Editor" is not – or MAY not be – fully compatible with the presence of several ".Net" versions.

______________________

Another info. I read: "Microsoft" decided to display BLANK ".Net" error messages, in non-English "Windows (or .Net)" versions! "Thanx" a whole lot, "M$", for such a "clever" decision!..


.



-- Edited by hiro on Sunday 27th of November 2016 05:22:48 PM

__________________
Page 1 of 1  sorted by
 
Quick Reply

Please log in to post quick replies.
cameyo -> Cameyo usage -> Package Editor not working - anymore


Create your own FREE Forum
Report Abuse 		Powered by ActiveBoard