Credit Card Number

I don't know if this is good or bad, and if either, in what way. But I have finally memorized my credit card number. I memorized the one I had before it, but it changed when it was lost, which was a good three years ago. Now, I can shop online without having to find my wallet, oh, and log on to the web site and pay the bill too.

GO-32 Satellite - APRS Operation

On my second attempt, I was able to transmit an APRS position report packet via the GO-32 satellite and receive the digipeated packet for confirmation.

How did I do it? Well, I followed Bob's directions on http://eng.usna.navy.mil/~bruninga/GO32-ops.html and used my new Kenwood TM-D710 with the dual band mobile antenna on top of Amy's van.

I'll try to explain the image below. It is a picture of the display on the Kenwood TM-D710. The top line basically says I'm in APRS 9600 bps mode and the time. The next few lines represent unsuccessful packets. The lines that matter are near the end.

NE3R-9>3Y2R2Q,4XTECH*:'i6(l ←v/]50W Mobile with 19" dual band whip=

That is my position report as I received it on the satellite's downlink frequency. The 4XTECH* represents the station that digipeated my packet.




Here is a pic of some random other packets I received during the pass.

Amy’s Van / Satellite Ground Station

I was home a little early from work today and had some time. So I checked the satellite schedule, and there was a good pass of AO-27 just after 4pm today. So I figured I would see how well the radio in Amy’s van worked for that. This is one case where the antenna not being straight up and down probably helped as it was sort of aimed right at the satellite.

I heard a few stations on, and then a break so I made a call. N5AFV from Huston Texas responded, then WA5KBH from Lake Charles Louisiana right after, and finally Leo, W7JPI from Sonoita, Arizona. All of this happened within about a minute. Since FM satellites only have one frequency for uplink that is shared among everyone, so you keep it brief, just exchange call sign and grid square.

I really need a recording device as I have a hard time operating the radio and writing at the same time. I think I have all the call signs right! The radio I was using was the Kenwood TM-D710 with a short dual band antenna on a lip mount.

WinDbg Output for my memory.dmp file

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 81c51e94, The address that the exception occurred at
Arg3: c23cc914, Trap Frame
Arg4: 00000000

Debugging Details:
------------------

Page bbe68 not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 7ffd500c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffd500c). Type ".hh dbgerr001" for details

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!HvpGetCellMapped+8c
81c51e94 8b4f04 mov ecx,dword ptr [edi+4]

TRAP_FRAME: c23cc914 -- (.trap 0xffffffffc23cc914)
ErrCode = 00000000
eax=00000efb ebx=0000013c ecx=000003ff edx=8e4ee1bc esi=8e4ee008 edi=00002310
eip=81c51e94 esp=c23cc988 ebp=c23cc9c8 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!HvpGetCellMapped+0x8c:
81c51e94 8b4f04 mov ecx,dword ptr [edi+4] ds:0023:00002314=????????
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: ieuser.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 81a7b5a0 to 81b12163

STACK_TEXT:
c23cc4d4 81a7b5a0 0000008e c0000005 81c51e94 nt!KeBugCheckEx+0x1e
c23cc8a4 81a9d63a c23cc8c0 00000000 c23cc914 nt!KiDispatchException+0x1a9
c23cc90c 81a9d5ee c23cc9c8 81c51e94 badb0d00 nt!CommonDispatchException+0x4a
c23cc9c8 81c22bff 8e4ee008 fffe5efb 00b135c0 nt!Kei386EoiHelper+0x186
c23cc9f4 81c2bb66 8e4ee008 8e4ee31c 00b135c0 nt!CmpAddInfoAfterParseFailure+0xcd
c23cca30 81afa215 0000000a 002c002c acdbdace nt!CmpFindSubKeyByName+0xae
c23cca7c 81a195b0 00000000 00000003 00000003 nt!EtwTraceContextSwap+0x14a
c23ccb78 81c8ae78 8b8f53f0 841102c8 84ae9008 hal!KfLowerIrql+0x64
c23ccc08 81c62fea 000003fc c23ccc60 00000040 nt!ObpLookupObjectName+0x11e
c23ccc68 81c59fa8 0381f234 841102c8 00000001 nt!ObOpenObjectByName+0x13c
c23ccd34 81c5a067 0381f318 00020019 0381f234 nt!CmOpenKey+0x1b1
c23ccd50 81a9ca7a 0381f318 00020019 0381f234 nt!NtOpenKey+0x16
c23ccd50 77819a94 0381f318 00020019 0381f234 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0381f270 00000000 00000000 00000000 00000000 0x77819a94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!HvpGetCellMapped+8c
81c51e94 8b4f04 mov ecx,dword ptr [edi+4]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!HvpGetCellMapped+8c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b12

FAILURE_BUCKET_ID: 0x8E_nt!HvpGetCellMapped+8c

BUCKET_ID: 0x8E_nt!HvpGetCellMapped+8c

Followup: MachineOwner
---------

Vista Crashed

For the first time since I started using Windows Vista it has crashed. Nothing serious that I can tell, just a blue screen of death and a reboot and all seems to be working.

Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 5/1/2008 10:36:06 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Planet-PC
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000008e (0xc0000005, 0x81c51e94, 0xc23cc914, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP.

I really don't have time right now to diagnose the problem. On Monday I upgraded the computer from two to four gigs of memory. It worked fine right after, but other than that, I haven't changed anything on the system. We'll see.

I just obtained my first copy of Windows Vista to install on my home computer. I hope that goes well!