michaelhong.com

You know, as the internet has grown, I’ve never really had a problem with people finding me through this domain (myname.com) and all of my other not-so-relevant online entities. I still don’t. But I feel weird putting myself out there and not getting to know YOU. And that’s not what I want… Sooo. Since no one reads this blog anyway, as of yesterday, I’ve moved my personal blog to a more community-oriented site. Don’t fret. I’ll keep posting here as infrequently as always with non-personal content (YouTube videos, most likely.) And I’ll leave my trail of posts, which have been spread out through this site and xanga and livejournal since I was a wee lad. And I’ll still be on myspace and facebook. If you want my new blog address, just ask! Most likely, it’s not you I’m worried about. It’s you!

http://sonyfanboy.ytmnd.com/

OMG. This guy is seriously awesome. I can see where he comes from, though. Sony has been messing with its fanbase big time. Not gonna lie, definitely gonna pick up PS3 and Wii at launch. Whether I’ll be able to afford any PS3 games is another question.

First, things are breaking down left and right. And to make my day the worst it could possibly be, I had the worst time with Aloha POS tonight at the restaurant. Somehow, the TRANS.LOG file for the day became corrupt. I lost all information for the day (server sales, reprints of checks, restaurant sales, and all associated reports). I tried to force close the day and move on to the next, but it refused because it couldn’t grind the TRANS.LOG. If any of you fellow Aloha users stumbled upon my site in hopes of a solution to the problem, I didn’t figure out how to solve mine. The only useful information I found was:

From http://www.tek-tips.com/viewthread.cfm?qid=1088470&page=2

To repair a corrupt log for the current day’s business, stop the FOH on all terminals, rename the Trans.log to BadTrans.log, open a command prompt and navigate to the Data folder on the file server. Use Grind.exe or GrindQ.exe to repair the transaction log on the file server using the following command line:

..\BIN\GRIND.EXE /FIXLOG BADTRANS.LOG

Grind does not alter the original transaction log (renamed BadTrans.log), but, instead, creates a new transaction log labeled Fixed.log. Once you repair the log, you must rename Fixed.log to Trans.log and restart the FOH terminals.

To repair a corrupt log for previous days business, open a command prompt and navigate to the dated folder on the file server, repair the transaction log in the dated folder using the following command line, and then manually regrind (refer to document AKBID1016) the dated folder:

..\BIN\GRIND.EXE /FIXLOG TRANS.LOG

Grind does not alter the original transaction log, but, instead, creates a new transaction log labeled Fixed.log. Create a backup copy of the original transaction log and rename Fixed.log to Trans.log.

I thought that it would work, but it didn’t. I then found a copy of Fixlog Utility for Aloha 5.2 and up from here. I think that would normally fix most errors, but my TRANS.LOG must have been F***CKED beyond belief.

Since I couldn’t move on to the next day, my solution was to backup my messed up TRANS.LOG in hopes of restoring it one day. In the meantime, I moved the previous day’s (functional) TRANS.LOG into the /DATA folder. It allowed me to move on to the next day. The only problem is that you’ll have two similar days worth of sales. In the meantime, I’ll try to figure out how to restore that corrupt log and post back with the solution.

P.S. I know absolutely zero of you care and/or understand this, but I just had to write it down and get it out of my head.

EDIT: It would be negligent of me to not thank my buddy Jacob for helping me through this trying time.