5 Latest Blog Entries
Forced to move.
by pechluck
on Thursday, July 03, 2008 7:11:42 PM
Recently at Otom...
by pechluck
on Saturday, March 01, 2008 11:26:14 AM
Moving to blogspot
by sunpech
on Tuesday, January 01, 2008 9:44:07 PM
Winter Break Plans :)
by joody
on Monday, December 17, 2007 11:33:03 PM
Shop on Amazon.com this Holiday Season!
by sunpech
on Wednesday, December 05, 2007 8:45:32 PM
News
Sunday, September 16, 2007
spongblog 2.0

It's been way too long since I've made a public update on the main page! But yes, work continues on for spongblog v2.0, but the first thing I want to do is move over all the data to a new server and then migrate it all into my new database structure. Yes, it's more difficult than it sounds.


Thursday, March 17, 2005
Code is coming along

  Some bugs and security holes were found in the past few weeks. I am working on fixing them. I do have an image gallery program working, if anyone wishes to use it for their site, please contact me.


Thursday, February 24, 2005
Navigation added to Blogs

  Navigation has been added to the user blogs for navigating to older blog entries. There is a problem with the 'Back' button (it will always take you back to the home page), and will be resolved shortly.


Thursday, February 17, 2005
Server is up

  The server is back up and most features are also. New features are being added slowly. Members are encouraged to login and test as well as update their accounts.


Menu
· Home
· About
· History
· Blogs
· Members


Members Login
Login:


Password:





Statistics
Page Views:
Users Online: 8
SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0x55555555; actual signature: 0xaaaaa555). It occurred during a read of page (1:7352) in database ID 1389 at offset 0x00000003970000 in file 'E:\MSSQL10.MSSQLSERVER\MSSQL\DATA\db117568153.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
© 1999-2005 (Well, not really)