OK, figured it out. What the QuickStart document neglects to mention is
that before performing step 4.2, you should have an *empty* CFC (I deleted
the primary partition that I had previously written with the physdiskwrite
program), and that before performing step 4.3 you need to write the image
to the CFC.
Norman H. Azadian Taegerishalde 13 CH-3110 Muensingen Switzerland
norman at azadian dot ch tel: +41 31 721 7855 fax: +41 31 55 898 55
Norman H. Azadian wrote:
> I'm experiencing the identical problem as Richard Davis (25 Feb).
> On my new WRAP.1D-2 with wrap-1.11.img written with physdiskwrite-0.5 to
> my 64MB CF, I'm getting:
> 01F0 Master 848A SanDisk SDCFB-64
> Phys C/H/S 490/8/32 Log C/H/S 490/8/32
> Console: internal video/keyboard
> BIOS drive C: is disk0
> BIOS 640kB/130048kB available memory
> FreeBSD/i386 bootstrap loader, Revision 0.8
> (root at nb dot neon1 dot net, Sat May 29 16:40:46 CEST 2004)
> /kernel text=0x182a80 data=0x1d66c+0x1ae38 syms=[0x4+0x28650+0x4+0x2f688]
> Hit [Enter] to boot immediately, or any other key for command prompt.
> Booting [kernel]...
> Interestingly, when I try it without the CFC installed, I get:
> 01F0 - no drive found !
> No boot device available, press Enter to continue.
> PC Engines WRAP.1C v1.03
> 640 KB Base Memory
> 130048 KB Extended Memory
> which would suggest that the BIOS is for the 1C, not my 1D card. I don't
> know if this is a problem or not.
> Another question I have is the startup. According to paragraph 4.2.4 of
> the QuickStart document, I should be getting something that looks like
> PC Engines WRAP platform
> tinyBIOS V1.4a (C)1997-2003 PC Engines
> 640 KB Base Memory
> 64512 KB Extended Memory
> 01F0 Master 848A HYPERSTONE FLASH DISK
> Phys C/H/S 497/4/32 Log C/H/S 31/32/63
> WRAP setup
> (9) 9600 baud *3* 38400 baud
> (C) CHS mode *L* LBA mode
> WRAP router platform 9 9/26/04
> (X) Xmodem upload (Q) Quit
> I don't get anything that looks like that, either with or without the CFC
> installed. What gives?
> BTW, it would be helpful in the quickstart to mention the name of a
> terminal emulator program or two under Linux. It's been a while since I
> had cause to use one, and it took me a while to remember that they're
> called 'minicom' and 'seyon'.