www.sandboxie.com :: View topic

Posted: Sun Jul 31, 2011 7:06 am

Hi.
I have tried everything about the sandbox settings, nothing helped (opening the IPC Paths, COM Classes etc. etc.).

(this is for the Virtual World 'Second Life', register at http://secondlife.com )
With the Firestorm Viewer beta 2 ( http://tinyurl.com/firestormviewer )
Viewers are the "browsers" for SL.
The viewer crashes when saving a script, if it's installed and started inside the sandbox.

(I have tried that out in a VirtualBox installation of Windows outside of sandbox and inside, it only crashes in sandboxie)

Posted: Mon Aug 01, 2011 5:01 pm

Alright, I'll look into it when I have a chance. Note that just looking at your post, the statement "the viewer crashes when saving a script" seems to vague and I might need more clarification later on.

Posted: Tue Aug 02, 2011 1:01 am

If you want, I'll show you what I mean "inworld" (SL).

Quote:

Scripts can make an object move, listen, talk, operate as a vehicle or weapon, change color, size or shape. A script can make an object listen to your words as well as talk back to you, scripts even let objects talk to each other.

The most basic object in Second Life is the "Prim" or primitive, the basic building block of all objects you can build in Second Life. When several prims are linked, they can each contain a script which speaks to the rest of the object via Link Messages. These are faster and more private than having objects "chat" or email each other. These are beyond the scope of this tutorial and we will instead focus on single scripts in a single prim.

Scripting is harder to learn than basic object manipulation, but is very rewarding once you make progress.

If you have built in Second Life, everything you can define in the edit window can be defined in a script. All interaction you see between objects or between avatars and objects is via scripts.

You don't have to learn the scripting language or anything, you just have to save a script in order to see what happens.

Posted: Tue Aug 02, 2011 6:27 pm

What I meant was if you could provide some concise step-by-step instructions as I would probably only be interested in reproducing the problem, and not learning my way around Second Life.

Posted: Tue Aug 02, 2011 7:25 pm

Of course of course.

Step 1:
First you register on:
https://join.secondlife.com/?lang=en-US
(Choose whatever "avatar" you like, if you prefer rabbits, go for it - lol).

Step 2:
Download the viewer from here
http://tinyurl.com/firestormviewer
(the newest one)

Step 3:
You install and run the viewer inside of a sandbox.
Start it, type in your name and password and log in.

Step 4:
Copy that link into your clipboard and send it into chat in SL:
secondlife:///app/group/76d84a6e-db0a-3759-e080-85a65b4cf016/about
Click on the link.
Click on the button "Join now".

Step 5:
Click on the "map" icon on the bottom.
Type into the search field: 'Rockcliffe Sandbox'
Click on the list entry with the same name
Click on 'teleport'

Step 6:
Once you're "loaded", press CTRL+4
Click on the ground
You created an "object",
click on "Inventory"-Tab of the window you have opened.
Click on "New Script".
Doubleclick the new script.
Delete the text that is shown in the "Script editor".
Copy and Paste the following code into the "Script editor":

Code:

default
{
state_entry()
{
llSay(0, "test!");
}
}

Click on "Save".

Step 7:
Your Viewer is crashed

Step 8:
?????

Step 9:
Profit.

Posted: Wed Aug 03, 2011 9:50 am

Thanks, those look like very clear instructions. As I said (or maybe just implied), I probably won't have an answer soon, but I will be looking into this at some point.

Posted: Wed Aug 03, 2011 5:45 pm

Is there a way I could fix the problem by myself?
The thing is just I'm blocked in scripting and would really want to make it working.

Thanks for your time, tzuk.
- blackbeat

Posted: Wed Aug 03, 2011 7:02 pm

Well, you can try to attach a debugger to the program which is going to crash. The debug log might give me a hint about the cause of the problem and allow me to figure out a quick fix. Note that you can install the debugger into the same sandbox as your Second Life programs so it shouldn't even mess up your system. More information here:

http://www.sandboxie.com/index.php?HowToUseWinDbg

You should focus on "Scenario 2: Attach the debugger to a running program" on that page.

Posted: Thu Aug 04, 2011 11:29 am

Hi, I did as you recommended.

The last lines while/after the crash are:

Code:

(3f8.784): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=101081b8 ebx=002fc3c0 ecx=00000000 edx=00000000 esi=002fc3c0 edi=101081b8
eip=7d237176 esp=0236ee2c ebp=0236ee40 iopl=0 nv up ei pl nz na pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00210206
*** ERROR: Symbol file could not be found. Defaulted to export symbols for F:\Program Files\Sandboxie\32\SbieDll.dll -
SbieDll!SbieDll_DeviceChange+0x8f7:
7d237176 668910 mov word ptr [eax],dx ds:002b:101081b8=0000

Posted: Thu Aug 04, 2011 5:12 pm

Thanks. Looks like the program is passing an invalid parameter to some Windows API which Sandboxie replaces. I'll need to check if the program does the same thing outside the sandbox, or if Sandboxie has something to do with that. Which means I'm still going to have to take a look at this myself. I'll try to look into this early next week. Sorry that I have to ask you to wait, but debug sessions like this typically take a few hours, so I have to find the time for it.

Posted: Thu Aug 04, 2011 10:08 pm

Thanks for the answer, tzuk.
I have found a pretty good replacement to that viewer so please take the time you need, it's not that important as I got more than enough alternatives.

Though there is something different I got problems with, SLVoice isn't working in the sandbox (it is for talking per microphone inworld).
Maybe you can check that, too - while you're at it.
I will make a special thread for that soon.

Posted: Fri Aug 05, 2011 12:53 pm

Blackbeat wrote:

I have found a pretty good replacement to that viewer

Alright, in that case perhaps I will wait until this problems pops up in a scenario that is simpler to work with. Smile

Posted: Sat Aug 06, 2011 9:58 am

Thing is, the viewer will be developed further and the alternative one not any more.
It is like the following version of the viewer I'm using at the moment.

What scenario would be easier to work with?

Posted: Sun Aug 07, 2011 1:31 pm

What I understood from your earlier post was that you're no longer interested in this particular script viewer, so I thought I would not have to bother with this. I look at problematic software all the time, but the thing with MMO games is they are always so tedious to look at, involving huge software downloads, and signing up to the service, and figuring out the game and so on. So what I meant was that perhaps at some point the same problem will surface with another software where it isn't so much hassle to look into it. But if you insist, then I will try to make time to look into this.

Posted: Mon Aug 08, 2011 1:23 pm

Well, i've been lurking for some time reading this particular thread.
Dont worry you dont have to download a huge client, the client is actually pretty small, around 20/30 MB. Most stuff is done server side.

Unfortunatly there is no way around about singing for the service.

I could try to repro the error, since i have sandboxie and im familiar with SL (been using it since 2007). Just dont use the same viewer as Blackbeat, but that can be easily fixed.

I'll see if i can make the viewer crash when i get back home. if that helps.

On a side note, tho you could consider SL a MMO, it really isnt a game, since there is no objetive, like in most popular MMO games, like go kill someone and turn in the quest. Think about it like a virtual world.