Nistune ROM Pack 2.3

If it isnt a problem or a suggestion it probably goes here.

Moderator: Matt

Post Reply
Matt
Site Admin
 

Posts: 9001
Joined: Sun Jan 29, 2006 1:45 am
Location: Adelaide, Australia
Contact:

Nistune ROM Pack 2.3

Post by Matt »

Another year... another ROM pack

We have had a few extra images added to the ROM pack since August last year so I've updated all the folders accordingly. The structure has changed

Type 1
Type 2
Type 34

Type 5 (S14 SR20DE, K11 CG10 half size ECU) not board supported yet
Type 6 (ECR33 RB25, BNCR33 RB26) not board supported (at all!)
TypeUnsupported (SR20VE models. not board supported)

Uninstall previous ROM pack 2.2 (and backup any files you had in there before doing this!) before putting ROM pack 2.3 on. Most people dont need this upgrade. Its mainly for tuners/distributors who want the extra files we have picked up along the way
bachig24u
 

Posts: 678
Joined: Mon Jun 01, 2009 11:46 pm
Location: Campbelltown, NSW
Contact:

Re: Nistune ROM Pack 2.3

Post by bachig24u »

Is the Rom pack 2.2 uninstaller supposed to remove file from 'documents' folder in W7?

its left all the factory files in place in their respective folders,
I though it may only leave the ones that were created by the user and not the system installer.
Matt
Site Admin
 

Posts: 9001
Joined: Sun Jan 29, 2006 1:45 am
Location: Adelaide, Australia
Contact:

Re: Nistune ROM Pack 2.3

Post by Matt »

Unfortunately not. The 2.2 installer only uninstalls the files where it places them and this was written before the 0.10.x releases

Since the 0.10.x release had to move the ROM pack to the new place to keep Windows Vista/7 happy (because saved files in Program Files were being put in a hidden folder) its now effectively broken the uninstall process

Potentially what I could do is make the 2.3 installer wipe out the 2.2 ROM pack but what I fear is I know that many people save their tunes in the ROM pack folders and I dont want to wipe out peoples tunes

Not sure what to do with this one from a development perspective

Best thing I can do is get the 2.3 installer to detect if the ROM pack 2.2 is in the Documents folder and rename it to say ROM_Pack_2.2 folder instead. I think this may be the best solution and then people can remove it themselves later if they wish. Will have a look at this tonight and test out the process and update on this thread
bachig24u
 

Posts: 678
Joined: Mon Jun 01, 2009 11:46 pm
Location: Campbelltown, NSW
Contact:

Re: Nistune ROM Pack 2.3

Post by bachig24u »

I just wanted to clarify, only because the typical warning was stated.. 'save your files' yadiyada

I thought the rom pack would overwrite files with the same name.
No problem, I'll just delete the oem bins and install 2.3.
Torque
 

Posts: 639
Joined: Wed Jun 16, 2010 10:08 am

Re: Nistune ROM Pack 2.3

Post by Torque »

I'm an avid defender of my rights as a user to place files where I want ;)

Therefore I moved the whole pack content to the folder structure where Nistune lives.
Other applications out there always leave a 'custom' install as an option.
That would be nice to have as well ..

My 'C' drive is not as big, and I don't want to clutter all the data over my system drive anyhow ..
From a performance standpoint of view it's kinda braindead anyhow that MS puts all the data on system-drive
(but that's another story)
Matt
Site Admin
 

Posts: 9001
Joined: Sun Jan 29, 2006 1:45 am
Location: Adelaide, Australia
Contact:

Re: Nistune ROM Pack 2.3

Post by Matt »

Updated to ROM Pack 2.3.1 version. There are just installer only changes given feedback above
I thought the rom pack would overwrite files with the same name.
Sometimes we change the filenames (eg update description) so this cannot be guaranteed
its left all the factory files in place in their respective folders
I've updated this now to search Program Files\Nistune, My Documents\Nistune or user selected folder\Nistune and change ROM_Pack to ROM_Pack_Backup. Folders can be manually deleted afterwards. As mentioned before I know a lot of people put their own tunes in these folders
Therefore I moved the whole pack content to the folder structure where Nistune lives.
Other applications out there always leave a 'custom' install as an option.
The installer should have done that but I used the wrong environment variable so it ended up hardcoded to My Documents. I've updated this to use the user selected folder instead now. Pete also found that last night. Tested out non-default locations and works well now

You will need to update the ROM pack location inside Nistune to avoid the 'locate file to sync' error so it can find files automatically
Therefore I moved the whole pack content to the folder structure where Nistune lives.
This will work fine (like always has for XP) but not for XP/Vista since any saved files end up in a locked hidden folder instead
Post Reply