Win 10 and Holley V4??
#1
Thread Starter
TECH Senior Member
iTrader: (3)
Joined: Jun 2004
Posts: 5,640
Likes: 69
From: GA, USA
Win 10 and Holley V4??
Am programming the Dominator, [Holley V4 version], and am having an issue w/ the screen going black..Am doing a pin map, and a short time after I try to make the gauge settings, the screen blacks out, with only a word or 2 left highlighted. I then have to hit the input button, and the screen relights. Shortly, same thing occurs.
It's probably something w/ Win 10 settings, as it's a new system for me. [No issues w/ XP and V2.]
Ne help is appreciated!
It's probably something w/ Win 10 settings, as it's a new system for me. [No issues w/ XP and V2.]
Ne help is appreciated!
#3
Thread Starter
TECH Senior Member
iTrader: (3)
Joined: Jun 2004
Posts: 5,640
Likes: 69
From: GA, USA
I just dumped the program, reinstalled it, made sure none of the old attempts at writing a tune were there.
The old program was copied to the new LT, and was in V2. I updated those tunes to V4. Not sure if the copy process corrupted something.
I am going to re-write a tune, into the fresh D/L, and see what happens.
I am using a custom tune, and changing what I need to, to fit this application.
More later....
The old program was copied to the new LT, and was in V2. I updated those tunes to V4. Not sure if the copy process corrupted something.
I am going to re-write a tune, into the fresh D/L, and see what happens.
I am using a custom tune, and changing what I need to, to fit this application.
More later....
#4
A recent WIN10 update had a multitude of bugs that they still haven't worked out. Most seemed to affect portables with SSD's. I would use an older OS for the time being, if possible.
#5
Thread Starter
TECH Senior Member
iTrader: (3)
Joined: Jun 2004
Posts: 5,640
Likes: 69
From: GA, USA
Oh oh...
It has a SSDD in it.
Might there be a location for getting any of the bug fixes? [Assuming there are any]. Windows update?
I have an old Compaq w/ XP Pro on it. I could update the V2 on it, and use it, til the fix is published, I guess.
Thanks for the headsup!