SRL Archive - MSI Suggestions

I think it shouldn't open and write to file each and every time MSI_Debug is called. Why? Because SSD and flash memory can get damaged because of that.

I'd like it to save my debug, but not as often as it currently does, as that wouldn't be good for my flash memory stick…

I'm not sure how to change this though

From: Zyt3x
I think it shouldn't open and write to file each and every time MSI_Debug is called. Why? Because SSD and flash memory can get damaged because of that.

I'd like it to save my debug, but not as often as it currently does, as that wouldn't be good for my flash memory stick…

I'm not sure how to change this though

Append it to a string. Then if (Length(theString) > ???) then add to file.

How does it damage your drives? Not saying you're wrong, just curious.

Not sure if it's harmful at all, but it sure is annoying as all hell flooding the debug box ;)

cbf'd to look through msi files atm though… =\

From: nose_smasher
Not sure if it's harmful at all, but it sure is annoying as all hell flooding the debug box ;)

cbf'd to look through msi files atm though… =\

That's what SetupVars[SETUP_DEBUG_LEVEL] is for.. If you set it to 0, nothing will show in the debug box.

Nice thanks, I only used MSI once lol… Guildy Miner… Failed on banking after 1 trip if anyones interesting in knowing ;)

From: nose_smasher
Nice thanks, I only used MSI once lol… Guildy Miner… Failed on banking after 1 trip if anyones interesting in knowing ;)

I'll get an account running in the guild as I haven't really yet, but it seems it could use some extra testing/tweaking.

Yeah Markus also had some trouble with it; although he has had some 5-7 hour reports, which is nice. :)

Proggy should probably be saved along with progress report…..

Does MSI really write to file at each time?

~RM

From: Coh3n
How does it damage your drives? Not saying you're wrong, just curious.

if i understand it correctly and SSD and Memory stick are essentially the same thing, a SSD has a lifespan, the more you write to it the faster its lifespan lowers until it reaches the point where it becomes an read only disk.

granted this is a very long long time (depending on disk size) its still limited depending on how much you write to the disk.

a small link about it better sources avalible

From: Sir R. Magician
Proggy should probably be saved along with progress report…..

Does MSI really write to file at each time?

~RM

Yes it does :/

From: bobzilla69
if i understand it correctly and SSD and Memory stick are essentially the same thing, a SSD has a lifespan, the more you write to it the faster its lifespan lowers until it reaches the point where it becomes an read only disk.

granted this is a very long long time (depending on disk size) its still limited depending on how much you write to the disk.

a small link about it better sources avalible

Thanks, that's correct :)

I meant debug should probably be saved along with proggy :p

How about…

Save Proggy to File
Get all Debug, Save Debug to file
Clear Debug
Print Proggy

?

~RM

From: Sir R. Magician
I meant debug should probably be saved along with proggy :p

How about…

Save Proggy to File
Get all Debug, Save Debug to file
Clear Debug
Print Proggy

?

~RM

Yes, that makes a lot more sense. :)

It has to get all the debug, including what's already in the file. But doing that only when the proggy is called should increase efficiency for sure.

Surely there's a method to just add to file..

if not, ask Dgby to write one

~RM

From: Sir R. Magician
Surely there's a method to just add to file..

if not, ask Dgby to write one

~RM

AppendFile?

I got a bit pissed today.. I though we had fixed this, so I just ran MSI without thinking about it, and when I re-opened my computer, 6 hours later I saw the led indicating that the USB were active blinking I just though "Noooooooooo!" :(

From: Zyt3x
I got a bit pissed today.. I though we had fixed this, so I just ran MSI without thinking about it, and when I re-opened my computer, 6 hours later I saw the led indicating that the USB were active blinking I just though "Noooooooooo!" :(

Why are you running Simba/scripts from a flash drive anyway?

I have too much to do right now, and honestly this isn't causing any problems so it's not on the top of my priority list. You're more than welcome to do it though.

From: Coh3n
Why are you running Simba/scripts from a flash drive anyway?

I have too much to do right now, and honestly this isn't causing any problems so it's not on the top of my priority list. You're more than welcome to do it though.

It's an USB stick that I sometimes are using on my other computers

The easiest way to do this would be to have it write the data to the file at progress report & ScriptTerminate, but that would mean run-time crashes wouldn't be recorded

From: Zyt3x
It's an USB stick that I sometimes are using on my other computers

The easiest way to do this would be to have it write the data to the file at progress report & ScriptTerminate, but that would mean run-time crashes wouldn't be recorded

IMO, it's not very SMART to run it from a USB. Just me though.

I'll get to this eventually if no one else does, but like I said, it's not my priority.

From: Coh3n
IMO, it's not very SMART to run it from a USB. Just me though.

…..


Are you being serious?

From: Zyt3x
…..


Are you being serious?

Why wouldn't I be?

From: Coh3n
Why wouldn't I be?

We're talking about SSD here, and whenever it's smart or not has nothing to do with the thread / problem

From: Zyt3x
We're talking about SSD here, and whenever it's smart or not has nothing to do with the thread / problem

I thought you were using a memory stick? And seeing as you're the only one who's had this problem, and you're using memory stick/SSD, I'd say it has something to do with the thread. =\

From: Coh3n
I thought you were using a memory stick? And seeing as you're the only one who's had this problem, and you're using memory stick/SSD, I'd say it has something to do with the thread. =\

I'm sorry. I'm in a bad mood :(
But essentially it doesn't have to anything to do with the thread, but dw about that :P

I'll look into ways to solve this problem later :)

From: Zyt3x
I'm sorry. I'm in a bad mood :(
But essentially it doesn't have to anything to do with the thread, but dw about that :P

I'll look into ways to solve this problem later :)

I guess you're right, I was just saying. I could be wrong, but I would think running Simba from a memory stick would run slower because it has less memory at it's disposal, hence your crashing issue. Of course, it could be something else entirely. :p

Generally, running from an USB stick is slow, depends on the quality of the stick, but still, I wouldn't run from an USB stick. As for the topic, I would prefer almost constant writing, like every 20 lines it would write to the file. That would be great.

Alright, I'll just make an SSD mode or something then :)

From: Zyt3x
Alright, I'll just make an SSD mode or something then :)

Add like a "LESS_CPU" option to MSI_SetupVars array. This can be the start of other things as well, such as object tracking for slower machines.

I'm working on this right now. As I'm looking at it, the way we do it isn't very efficient, in many ways.

What I'm going to try is creating the file on startup, then keeping it open throughout runtime, then closing it on script terminate. Plus, I'll be using AppendFile, rather than clearing the file, then rewriting EVERYTHING back to it.

E: This is now committed to my fork, along with a bunch of other things. Click here for details.