SRL Archive - S.M.A.R.T. Questions and Answers.

Hello all,

Recently I reformatted my computer, re-installed the latest Scar (so now Im using 3.2 instead of 3.15B) along with Reflection.

Unfortunately, I ran into the problem with an Access Violation.

[Runtime Error] : Exception: Access violation at address 6720456E in module 'Embedded_SMART.dll'. Read of address 00000000 in line 85 in script C:\Program Files\SCAR 3.20\includes\SRL/SRL/Misc/Smart.scar

I read several other threads and took the following actions:

• Updated the Embedded_SMART.dll to the new version (4.2 if memory serves)
• Replaced the underscore with a space and also tried with removing the space
• Updated my Worlds.ini
• Insured that I have the latest SRL revision (Rev 4#31 if memory serves)
• Made sure that I am logged into an admin account, even downloaded most things I would have done later (like the .NET Framework).

What else could it be? I don't know, quite frankly, I'm stumped. Used to run so nicely with SMART too…

I would try re-installing Everything and re-replacing the Smart.dll

Will try that and edit this post.

Edit:
No luck.

I uninstalled it and removed the few files it left behind.
Went and downloaded Scar 3.15B (as I've used SMART with it just a week ago).
Allowed it to update, replaced the Embedded SMART.dll and still no luck :(

Have you tried the Embedded_SMART.dll from the Reflection revision? I'm using that with SCAR 3.20 RC3 and it's working beautifully.

Yes, that is the Embedded_SMART.dll that I have been using.

This is quite odd. Try asking on the IRC channel.

Open up the script and find

Setupsrl;

and above it paste this in

SMARTSetupEx(1, False, True, False);
Wait(5000);
SetTargetDC(SmartGetDC);
repeat
wait(100);
until(SmartGetColor(253, 233)<>1118604);

Hope this helps :D

From: Dark Arcana
Open up the script and find



and above it paste this in



Hope this helps :D

I am using a script I've used for a long time, and very recently at that (the day before I reformatted).

I've also tried using this SMART test script, which uses the method you just described.

Problem fixed.

Never did like that version of Windows, for multiple reasons. This just added one more reason to the list. Installed new version of windows, set it all up, runs perfectly.