The Hoju Saram

Thursday, February 28, 2008

Tried to go korean food shopping

Here is my list... It seems it is hard to find most of this stuff in brisbane. I can find substitute products, but I will keep trying to find the genuine items.

1.돌아온 왕꿈틀이
2. 몽고 순 간장
3. 한일 본고장 가쓰오 생우동
4.오리온 고래밥(볶음)
5.오리온 고소미
6.롯데 꼬깔콘 고소한 맛
7. 롯데 꼬깔콘 군옥수수맛
8..오리온 초코파이
9.롯데 자일리톨 껌
10.송학 비빔쫄면 460g
11.오뚜기 마요네즈
12.오뚜기 참기름
13. 롯데 레쓰비 캔 커피 마일드
No.8 is chocopie. Yum !! (Which I can find)
It turns out it has it's very own website..

Tuesday, February 26, 2008

Space 김치

Proving once again that South Korea is now a economic powerhouse. The government has invested( wasted??) millions in getting kimchi into space ready for the very first South Korea first astronaut.

Three top government research institutes spent millions of dollars and several years perfecting a version of kimchi that would not turn dangerous when exposed to cosmic rays or other forms of radiation and would not put off non-Korean astronauts with its pungency.
Read full story


Monday, February 25, 2008

Another step towards wireless video kiosks

I noticed this article this morning.

One potential use of the wireless transceiver chip has owners of handheld media devices being able to step up to a shopping centre kiosk and download high-definition files of movies and TV shows in the blink of an eye.

Seems like it won't be too long before this become a reality. I've talked about this idea before here and here.

It will be a happy day when I can go to the local train station and get a hot coffee in a can and a HD-Movie Bundle from the vending machine.

Labels: ,

Friday, February 08, 2008

ADAM setup for AD .net memebership provider

I have been working on a project lately called RAI. I am not going to talk about it here, but basically it is an external facing and internal facing application for one of the organisations I provide IT services for. For the external client we decided to use ADAM for the authentication source, so I started to have a look at using ADAM and the AD membership provider. Well lets just say that was 5 days I will never get back. So just in case you are ever in a situation where you need to get the AD membership provider to work with ADAM these are the step to installing ADAM so it is setup ready for you.

ADAM can be downloaded from Microsoft at

The following steps are required to install ADAM for use with the Active Directory .Net membership provider.

1. Run the ADAM installer.
2. Select “unique instance” , press next
3. Set the instance name to your project name in this case I am using “RAI” , press next
4. Set the LDAP port to 50000 and the SSL port to 50001 ,press next
5. Select “Yes, Create an application directory partition” and set the partition name to “O=[projectname]” , again in this case I use RAI press next.
6. Accept default or select a suitable place for the files , press next
7. Choose default for Service Account Selection
8. Choose "Currently logged on account" for ADAM Adminstrators
9. Import "MS-InetOrgPerson", "MS-User" and "MS-Userproxy"
10. Click next to complete the install
The ADAM instance for RAI will now be installed on the application server. It must now be configured.

11. Open "ADAM ADSI Edit" from the ADAM program group in your start menu
12. Select "Action->Connect to..."
13. For name use your projectname
14. Alter the correct portnumber in the Port textbox (50000)
15. Change to “Well-Known naming context” and select “Schema” and then press OK

16. Right click on the schema item and select new object. From the class menu select “AttributeSchema”.
17. Create the following 5 new attribute schema entries

cn: PwdQuestion
OMSyntax: 64
lDAPDisplayName: PwdQuestion
isSingleValued: TRUE
AttributeID: 1.2.840.113556.

cn: PwdAnswer
OMSyntax: 64
lDAPDisplayName: PwdAnswer
isSingleValued: TRUE
AttributeID: 1.2.840.113556.

cn: FailedPwdCount
OMSyntax: 2
lDAPDisplayName: FailedPwdCount
isSingleValued: TRUE
AttributeID: 1.2.840.113556.

cn: FailedPwdAnswerTime
OMSyntax: 65
lDAPDisplayName: FailedPwdAnswerTime
isSingleValued: TRUE
AttributeID: 1.2.840.113556.

cn: FailedPwdLockOutTime
OMSyntax: 65
lDAPDisplayName: FailedPwdLockOutTime
isSingleValued: TRUE
AttributeID: 1.2.840.113556.

18. Close the "ADAM ADSIedit" program
19. The user schema object in the ADAM instance needs to be modified to support the additional attributes created in step 17. This needs to be done via the mmc ADAM snap-in. To create an MMC file for the ADAM Schema snap-in
20. From the taskbar Click Start, click Run, type mmc /a, and then click OK.
21. On the File menu, click Add/Remove Snap-in, and then click Add.
22. In Available Standalone Snap-ins, click ADAM Schema, click Add, click Close, and then click OK.

23. To connect to your ADAM instance through ADAM Schema, in the console tree, right-click ADAM Schema, click Change ADAM Server, and then complete the dialog box as follows

24. Click OK
25. In the left hand pane double click the “classes” folder to view the list of schema classes
26. Scroll down to “user” the user object and right click on it. Select properties and then select the attributes tab.

Add the five attributes create in step 21. cn: PwdQuestion , PwdAnswer, FailedPwdCount, FailedPwdAnswerTime, FailedPwdLockOutTime

27. Click OK and close the mmc console. The schema changes are complete. You must restart the ADAM service before you continue.
28. Open the windows services control panel from administrative tools and restart the ADAM service.

29. Close the services control panel.
30. Open the ADSI Edit tool again. Right Click on the [projectname] connection and select “settings”. Change the connection node to "Distinguished name" and enter “O=RAI”
31. Click "Ok"
32. Right-click the "O=RAI"-folder and select "New" and "Object..". Choose "organizationalUnit" and name it "Users", click next and then click finish.
33. Right-click the new "OU=Users"-folder and select "New" and "Object...". Select "user" and give the user the name "ADAMAdmin", click next and then click finish.
34. Right-click the "CN=ADAMAdmin" -account and choose "Reset password". Enter a password you will remember
35. Double-click the "CN=ADAMAdmin"-user and set the "msDS-UserAccountDisabled" to False , click ok and close the properties box.
36. Go to the "CN=Roles"-folder and double-click the "Administrators"-account. Locate the "member" attribute and double-click it. Choose "Add ADAM-account" and enter the distinguished name of your newly created user (CN=ADAMAdmin,OU=Users,O=RAI). Click the Ok-buttons to close the editor.
37. Right-click the root of the Connection in the left hand pane. Select “Settings” from the menu.

Change to “Well-Known naming context” and select “Configuration” and then press OK.
38. Navigate to CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration,CN={GUID of the ADAM}.
39. Right-click CN=Directory Service and select Properties.
40. Double-click the dSHeuristics attribute.
41. Set the value to 0000000001001 and click OK.
42. Click OK to the CN=Directory Service properties box.
43. The ADAM configuration is now complete.

You will obviously need to setup your application web.config to use this ADAM instance. Have a look at and for this information.

Long time no blog again !!

Well I have not blogged for a long long time. So here is a dot point update of what has been happening.
  • Went on leave from work for 8 weeks

  • Went to Japan for about 4 days , saw taku and toki's family and went back to tokyo disney, my son got to see asimo up really really close so he was very happy. ( the pic is asimo at his home base )

  • Went to korea for 2 weeks to pickup my daughter. Met up with heaps of friends and ate so much traditional korea food I almost exploded. I did however get to eat buffer fish for the first time so that was great

  • Came home and sat around for a few weeks with my new extended family

  • Went back to work.

Adoption law in Queensland means that I can't leave OZ for a year, so I won't be going anywhere to exciting until 2009. Although if I can rangle it I want to be back in FIJI for christmas.