I've got several tunes scheduled this week, and I need my Pro back up and running asap!!!!! I've cleared neptune, unloaded/reloaded crome, did a system restore, nothing works. Can anyone help me asap please??

 

Download 1.5, I think he built in a Date Expiration

http://www.tunewithcrome.com/download/crome1.5.zip

 

Yep, I think that's exactly what happened. I was about to set back the system clock. Ended up removing temp files, prior system files, then loaded 1.5.0 that I found through searching pgmfi.org and I'm back working....THANK GOD! I WAS TERRIFIED.

 

expire date bomb..
force to use 1.5

 

From the title you make it sound like NepTune caused it. You may want to clear that up.

 

i had this same problem a couple days ago.

thanks chris

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by HRTuning &raquo;</TD></TR><TR><TD CLASS="quote">From the title you make it sound like NepTune caused it. You may want to clear that up. </TD></TR></TABLE>

Thought ya'll put some Crome seeking wild bug in that software download....

NEPTUNE is NOT TO BLAME

 

cooool....

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by norconex &raquo;</TD></TR><TR><TD CLASS="quote">Download 1.5, I think he built in a Date Expiration</TD></TR></TABLE>
Why would you do something like that ?
There are a couple of practices in this industry that baffle me. Jealously guarding software so much that your market becomes limited is one thing (not talking about Crome-specifically) that makes little sense. The Apexi Power FC would probably have sold quite a few more units if the laptop software for tuning it was more readily available to tuners, for example. Another thing that kind of makes no sense is password protected maps-in Greddy EManage for example. If a customer pays to have his car tuned, isn't the map his property? If the same customer chooses to go to another shop for tuning, why should he have to pay for a complete tune again?
These proprietary maps that come with Greddy kits are no prize winners in the first place.
We believe that once the customer has paid for a tune, it's his to modify, or to pay someone else to modify if he so desires. He can even give it to his buddy with similar mods, at his buddies' own risk, of course.
Making it difficult for tuners to obtain software, writing code that causes the software to stop functioning after a certain date, and locking maps, are all counterproductive IMHO.
I am not saying that everything should be free. The people who develop these tools should be compensated for their hard work; that's what licensing fees are for
Others may dissent

 

I think I remember reading somewhere that in the case of some of the rom editors, Crome, uberdata, TurboEdit. It is done to remind the code writers about updating certain codes or fixes that may have been worked out. Rather than putting out a minor update every other week. You have to remember that a lot of these programs are always going to be in a beta type version. They are always begin upgraded and having little bugs fixed. That is what DIY PGMFI is all about. I myself have no idea how to code so I just pay for the software to keep the development going.


Modified by GhostAccord at 3:33 PM 6/4/2008

 

Well, personally I feel that Crome is going to get away with certain quirks because its a cheap system. You make sacrifices in the interest of saving money. For those where quality and consistency is more important, well there are certainly up and coming systems that while still affordable, answer that call.

Crome serves a purpose in my book, but the days of tuning Crome are getting old. The quirks get more annoying when you have other guys on the block with a better product that cost only a slight bit more to run. That's where I'm headed, plain and simple.

 

Just tried to use Crome for the first time in about a week. It's asking for the reg string again. Even better, Crome 1.5 won't even run, it generates an error and shuts down. Version 1.2, 1.48, and 1.49 work, but now they are the unlicensed versions. I see that on PGMFI.ORG that I am not the only one experiencing the issue. There are work arounds that some guys are trying, but why write a time bomb into the software in the first place? Waiting for a response from John Cui to see what he is going to say...
I love Hondata

 

it shouldnt ask for a Reg String unless you did a complete reinstall and over write the Crome Directory.

There is a file in there called REGISTER, back that file up. As long as you dont reinstall your whole operating system, you can put that file in the same Crome directory and it will be PRO featured.

Also, if you keep the original email from John, it 'should' let you copy/paste that original reg string into the software, unless your SERIAL ID has changed (which it shouldnt if you have the same operating system.

 

If you use the latest full release of Crome (1.2 IIRC) there are no issues. Only the newer beta versions have the expiring problem, reverting to the latest actual non-beta release will always solve that.


As far as passwords and stuff... I am on the fence about it. I agree that someone who pays for a tune should have access to it, since they paid for it. On the other hand, as a business, I don't like when customers have access because there are a lot of stupid people who will edit thier maps and when the engine blows up or something, they can come back and blame you. I guess that's a normal risk we take on any job we do on people's cars though.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by norconex &raquo;</TD></TR><TR><TD CLASS="quote">There is a file in there called REGISTER, back that file up. As long as you dont reinstall your whole operating system, you can put that file in the same Crome directory and it will be PRO featured.</TD></TR></TABLE>
I figured it out. I replaced the processor in my laptop and it changed the ID a few digits. I had a similar issue a year ago when I replaced a hard drive. Crome is sensitive to hardware changes that none of my other tuning software even blinks at. Thanks to John Cui I am up and running again. It still sucks that 1.48 and 1.49 don't work unless I set my clock back to before June 1st