question 1:
I am programming an SC-IAT with a practisetrail at the very beginning and then 2 test trials (two seperate SC-IAT's - 2 brands). There aren't any practisetrails before the test trails of which I want to use the data, so the D's I am using are the d1 (1st test) and d2 (2nd test), see below:
/ d1 = (m2a - m1a) / expressions.sda
/ d2 = (m2b - m1b) / expressions.sdb
The D computed from m2a and m1a is the D computed from practice trials (see: http://www.millisecond.com/forums/Topic3444.aspx). Since you don't have any practice trials, I find it very likely that you simply broke the scoring in the process of modifying the original script. See this thread for a more detailed explanation of the different means involved in computing D: http://www.millisecond.com/community/forums/t/1370.aspx.
Suprisingly one of my d1 was 1.04. Just recently I found out that it is possible to have a d between -2 and +2, and I assume that this means that someone has an extremely strong positive attitude towards that category?!
Again, since you probably broke the scoring, I wouldn't trust this value in the first place. However, it is correct that D varies between -2 and +2 and as such a value of 1.04 is theoretically possible (but should be rare in practice). Whether the respective value reflects a strong positive or a strong negative association depends on how you've set up the different categories in your IAT. The first thread I referenced has more info on that, however...
Unfortunately the <% expressions.attitude %> in the summary changed to the negative - so it said 'onaantrekkelijk' instead of 'aantrekkelijk' (unattractive/attractive)
... suggests that (a) you may have entered categories in the wrong way and/or (b) you broke the scoring.
To say 'aantrekkelijk' I assume that the d1 has be >= 0 and not untill 1.
No, see my point above.
And what the chances are that a D can be above 1, since then it might be a good idea to incorparte something like D >= 1. values.magnitude = extreem.
D scores above 1 should be relatively rare in practice, however this may differ for some domains. You should check the relevant literature, especially look for available meta-analyses. However, it is way more likely that you broke the scoring (yes, I know I'm repeating myself) and the D scores you're getting actually don't mean anything. That said, I don't think that introducing another scoring quantifier ("extreme") is warranted, but go ahead and do whatever you want.
question 2: As I understand the improved algorith incorparates error penalties.
Yes.
I assume this means someones D is lower if there responces have a lot of errors?
No. If a participant makes the same amount of errors in both pairings (compatible and incompatible), D will be basically unaffected. If a participant makes systematic errors (e.g. only in the incompatible pairing), the resulting D will be larger.
Could this error penalty also be incorparted in the calculation of the D for the data file? without having to use SPSS?
All the IAT scripts available from millisecond.com adhere to the conventions of Greenwald et al.'s "improved" scoring algorithm, i.e. error penalties are included. However, you probably broke the scoring.
question 3: Now I can't see the D's in the data file, to see them do I only have to remove '/ recorddata = false' from the summary?
Because you probably broke the scoring. Removing the 'recorddata' attribute won't help here, but feel free to try nevertheless.
script included
No -- you *always* post random data files for some reason.
~Dave