Author Topic: AfterBlock - Blockland Desktop Program [UPDATE 1.2 RELEASED]  (Read 40694 times)

Code: [Select]
ERROR in
action number 1
of Create Event
for object sst:

Error defining external function.
Help?


Stupid IcyGamma running into walls..

The Programs File X86 is just like the normal one, except it holds different things. I have it and I'm using Windows 7. Don"t worry about it, I doubt that anything will happen to it.

P.S. Apparently the internet has run out of IPv4 addresses. O_O

ADD: Also, Steath PM me or IRC me. I got a surprise to show you.
X86 is 32Bit Apps The Normal one is for 64Bit Apps
That is for all 64Bit Windows Systems

Are you running version 1.1? That should self extract all the DLLs. If you continue to get the problem, please do the following and report your experience.

1.  Launch AfterBlock
2.  When the window appears with the logo, press Control and D at the same time on your keyboard (before it welcomes you)!
3.  The debugger will appear, under the "diagnoses" tab press the execute button next to "Check DLL bank" and "Check file structure"
4.  If you are missing any DLLs, fix them by executing the repair feature below the diagnoses for the appropriate DLL
5.  Run the check again and report back


Before I was getting error, after downloading 1.1 I get again error.

I did what you said there but it change nothing, help?

What did the diagnoses report?

What did the diagnoses report?

Function executed successfully.
7 out of 7 core components were detected.

and


Function executed successfully.
2 out of 2 core folders were detected.

I'm just going to take a guess and say that that is going to happen to me. Downloading now.

Mr.Lol how'd you install the update?

I'm just going to take a guess and say that that is going to happen to me. Downloading now.

Mr.Lol how'd you install the update?

I removed the 1.0 version

I re-downloaded AfterBlock (1.1 version)

I re-downloaded afterblock and only got the application in the .zip. Is this normal?

I re-downloaded afterblock and only got the application in the .zip. Is this normal?

Me too I had that, I started it then I check all the files we're there.

0 out of 7 core components were detected
2 out of 2 core folders were detected
3 out of 4 elements of additional content were detected

When I click one of the repair buttons it says it was executed successfully. It still doesn't find them. Do I need to restart?

EDIT: I restarted and the components and element still can't be found. Is there any way to download them manually?
« Last Edit: February 06, 2011, 06:10:09 AM by Freeze »

Blockland uses a custom installer and seems to install itself into Program Files (as it was probably created in the days when 64bit was rare), whereas a newer installer (or maybe an .msi) would install into Program Files (x86) because that's where 32bit applications on 64bit systems seem to belong.

Correct, except for the Blockland installer part.
Blockland installer is built using NSIS (Nullsoft Scriptable Installer System). On Windows Vista and newer it's defaulting to C:\Blockland (provided your system drive is called C) because of UAC (user account control).
So, the only case where it would default to Program Files (x86) would be either if you ran Windows XP Professional x64 (which is quite uncommon and I don't know if it had the PFx86 folder) or if you turned of UAC (which I'm not sure would trigger it to default to PFx86).

X86 is 32Bit Apps The Normal one is for 64Bit Apps
That is for all 64Bit Windows Systems
The separation is good for two things.
  • It keeps the user informed of which applications are ran through WoW64 (Windows 32-bit on Windows 64-bit) (the wrapper which lets you run 32-bit applications under 64-bit)
  • Since 64-bit applications can't use 32-bit libraries and vice versa, this creates different "namespaces" where the applications can load libraries, and some applications might even install twice, to allow for 32-bit plugins
« Last Edit: February 06, 2011, 07:37:43 AM by DontCare4Free »

Bump, I want this problem to be fixed. :C

i get this when i load it:

Quote from: Afterblock Blog
Major Bug Uncovered
I have uncovered a major bug. Due to a wee oversight (major understatement) I seem to have heavily relied on use of reading and writing to the working directory, and not the program directory. This means if you add a shortcut to the start menu for example, all data and content is unpacked into an awkward destination somewhere around the start menu folders hidden away on your hard drive. This may even be why some users are getting bugs when launching!

The solution is simple. I must change working_directory to program_directory. But this is going to be a bitch because it reads and writes a lot. Expect a further update soon.

Thankfully, this error won't really affect you assuming you are running AB from a contained  folder and using simple shortcuts if you want to cleanly access AfterBlock via the start menu or your desktop. However it may result in a messy update for those who have experienced the bug. This issue affects users of both 1.0 and 1.1.

0 out of 7 core components were detected
2 out of 2 core folders were detected
3 out of 4 elements of additional content were detected

That is really really weird and I'm baffled.
It can detect the directories, and most of the additional data but not the DLLs. It looks like it can't read in the Data folder. All the DLLs and the single piece of additional media held in the Data folder are unreadable....

This is strange, but of extreme help. I'll look into it ASAP.