PDA

View Full Version : Script Error on Line 169


tavo
01-12-2006, 10:49 PM
Let the 102 Glitching continue....
LETS TRY NEW DELAY
Glitch Delay = 0329
VCC = 4A

-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+----++++-+-+-+-+-NoRsp+--++-+-+-+-+-++
Script Error on Line 169 Sc.Read: Timeout Reading Data From Card - 27 Bytes Requested, 26 Bytes Read

Is anybody else getting these errors?? Sometimes the script does run for about 2 minutes but then I get this error, 2 minutes is the longest it will run. I have been trying to open a 102 for the past week and getting no results. I have tried differnt dip settings on the t911 mod and no go. I also changed the settings on Win Explorer 5.0 and tried diffrent settings on the ROM102_ND13_AOFF-INTERCEPT-autoVCC_20 script itself and no luck. I do get a good ++-- mix but no INTERCEPT. Im using a 20ohm Rehostat and a 5K Pot for the rom 10's. The 10's pop in less than a minute so I'm open to suggestions guys.. Thanks...

#40Fan
01-12-2006, 11:47 PM
Use dips 1 and 3 on for the 102s. Adjust the pot to a higher resistance until you get the NoCMD4 error, then back it down a hair and let it run.

tavo
01-13-2006, 03:24 AM
Use dips 1 and 3 on for the 102s. Adjust the pot to a higher resistance until you get the NoCMD4 error, then back it down a hair and let it run.

Yes I've tried this as in a previous post of yours.I adjust the pot to get the NoCMD4 error then back it up just a bit but the freaking script just stops, I mean as it's running it stops half way and gives me the 169 error.. It stays +-+-+-+ half way the page. That sucks!!!

I'm using these settings:
VCCStart = &h2f
VCCLimit = &h02
DelayStart = &h320
DelayLimit = &h38a
GlitchMax = 8
GlitchMin = 6
trys = 100
mix = 0.
Dips 1 and 3 on.
In fact I think I've tried all the settings suggested in the Rom 10X Glitching! What's Working For You thread that u started and gone thru all 13 pages!!!

tavo
01-22-2006, 01:42 AM
Well I'm using Win 98 now and seems to be running OK. The script does not stop like in Windows XP Home, don't know what the deal is?? I'm using the Ufp16 and Newd13. I'm running the Rom 102 AOFF Intercept, see what happens. The script has been running now for 16 hrs non stop with no intercept. I'm using dip 1 sitch only on, the other dip settings don't seem to give me the +-+-+-. Well that's why it's called testing... Lets wait and see what happens... I'm open to suggestions...

harrybuckman
01-22-2006, 03:03 AM
yes I have the same problem on xp corp pc works great and the other script error 169.

There is no fix, I have searched high and low, the problem PC works great with rom 3,10 and 11 glitching scripts and all h and hu winex scripts but not rom 102 winex scripts.

The PC has the exact same updates and setup as the other that works

so to unlock 102's on the problem PC I use ftapirates rom102unlocker. It is a VB app that does not suffer from the timeouts. Pops my 102's in seconds on my problem PC.

Don't worry I can assure you your problem is not your loader or cable or winex settings. It is a PC problem.

Go get ftapirates rom102unlocker and pop some 102's. Hey it looks cooler that winex too.

traylehr
01-22-2006, 09:11 PM
you need to refine your settings . shouldnt have to run the program as long as your letting it run ,with most programs like these they end up looping cards . the card will pop with in a few min. if the program is set correct , i've found that not all loaders act the same , & each takes its own settings . you do need to bring down the voltage , above it said something like 4A , way too high .05 - 20 is where you should try/start , & as stated the resistance/pot turn it till it noresp , than back a bit , short glitches are ok , make sure you have a good pot , bad ones will keep it from working correctly . delay setting- 320 / 350 also a good place to start . remember to change the voltage in all the places - at the top & two places in the middle of the script (where its set at 40/&h40 ) to 20 . once your loader pops the card youll know where to refine even more for quicker opennings.

harrybuckman
01-23-2006, 09:25 AM
If the guy that had the error on line 169 is still with us, do what I have said above,

End of story problem solved




Unless someone can enliten me with the real way to fix the winex error on 169...


I doubt it...

harrybuckman
01-23-2006, 09:28 AM
The above script error pertains to pc hardware compatibility, not vcc settings. I've edited the script's vcc's start and return, also reversing the NoScript+ values. The same pc that unlocked rom3/10/11's never had script error 169, but changing the receive timeout option will let the script continue. I can use the same exact voltage and vcc's on a desktop pc and never get errors.
The laptop I do get errors on, I have yet to ever loop a single card. Unlocks between 2-5 minutes. Fastest one unlocked in 1 second.


yes completely correct no loops at all. ftapirates rom102unlocker is the answer.

harrybuckman
01-23-2006, 09:30 AM
you need to refine your settings . shouldnt have to run the program as long as your letting it run ,with most programs like these they end up looping cards . the card will pop with in a few min. if the program is set correct , i've found that not all loaders act the same , & each takes its own settings . you do need to bring down the voltage , above it said something like 4A , way too high .05 - 20 is where you should try/start , & as stated the resistance/pot turn it till it noresp , than back a bit , short glitches are ok , make sure you have a good pot , bad ones will keep it from working correctly . delay setting- 320 / 350 also a good place to start . remember to change the voltage in all the places - at the top & two places in the middle of the script (where its set at 40/&h40 ) to 20 . once your loader pops the card youll know where to refine even more for quicker opennings.



You never read my post shame on you.LOL

This is a PC problem.

traylehr
01-23-2006, 11:44 PM
i also have yet to loop a 101,102 but ! what i was trying to stress was glitching these cards for extended periods of time isnt good , in any instance.

harrybuckman
01-24-2006, 05:07 AM
i also have yet to loop a 101,102 but ! what i was trying to stress was glitching these cards for extended periods of time isnt good , in any instance.


Maybe I should read more carefully LOL, I wonder if the thread starter had any luck?

tavo
01-24-2006, 05:31 AM
Guys I'm still here.. Well I've now tried on 98 and no go. Harry balzac is right.. I just checked the "ignore recieve timeouts" and it's running pretty good on XP. Yes it's running on a laptop... I've tried evey pot setting and every dip setting with no luck what so ever. I'm using a rehostat for the Rom 10x and a trim pot for the Rom 10's. I know my mod is good and working because I have unlocked a couple of 10's but not a single 10x in either 98 or XP. The only good setting on the t911 seems to be the 1 dip. That's the only switch that will give me a good +-+- mix. The other's give me all --------- or Bad CMD04 response. Yes I know back off just a hair and try again!! I've tried all the freaking TRIM POT, REHOSTAT T911 and Script settings (102 Intercept) and NADA!! I'm running on 9volts. OH and Harrybuckman yes I have also tried the FTA script, you mean the Nagra Master Beta right? Well I tried it on 98 let's see what happens on XP. It's exactly the same script and settings though as the 102 intercept, I doubt anything will change. Well thanks for your suggestions guys and let me hit this freaking 102!! As I write this reply, the script has been running on XP for about 30 min on +-+-+-+-+-+- no intercept. Will post my results...

harrybuckman
01-29-2006, 08:32 PM
Try changing your power supply voltage between 6-9 volts, try a different switch. I found the only think that worked on my absolute was switch 3 at the lowest possable pot resistance.

DrSagan
01-29-2006, 08:54 PM
The problem is likely that the computer runs the script faster because the computer is faster. I highly doubt it is a winxp problem. If you add a sc.delay(20) above the sc.read it will probably solve the problem too. It may not matter in the particular script you are working on, but telling winex to ignore a problem might create another. If sc.delay(20) doesn't work, try 30 or 40