The site now says you’re green (Good). 😉

Still says you link to iwarp, if you’ve removed it it may just need to rescan your site.

Its always great to hear we;ve brought another one to the dark side. 😉

As for the lens, when it broke did it actually break into smaller pieces? If so, you can probably tilt the VB and shake them out, as you would anything thats fallen inside anything else.
If its not that small, you should still be able to get it out. After all, you got it in there.

IIRC the ROM listed as ‘good’ in GoodVBoy (and hence most ROM sites) is in fact bad. I remember a few of the ROMs being mislabelled.

Try locating the ‘other’ Nester ROMs and trying those.

Ah, so it isn’t just me then.

It’s always great to hear that another VB has been revived instead of being thrown away! 😀

It sounds like the display cables have come loose.
This link provides some more information about it.

…And here I know people b*tching about how the prices of (rare) games are dropping.

…Damn, should have gotten Water World and Jack Bros sooner… 🙁

VeeBee is also what I call it.

Thats why I names my dev kit (and website) that. 😛

[size=1]…I should really get my site back up…

Nice. I just gained 5% 😀

…A question though: with the column headings, the first column (‘C’ for games and ‘I’ for hardware), stand for the items themselves, correct?
At first I thought the ‘C’ stood for (plastic dust) cover, but just realised the hardware had ‘I’ instead.

jorgeche: I haven’t touched gccVB in ages, and since then its gone an overhaul, so the following may not work right.
This is the timing code from my Zelda demo. I just tested the ROM in the latest (at least I think it is) copy of Reality Boy, and it seems to be running at the correct speed.
I actually used the ROM timer interrupt to increment a counter that I could then use to calculate the time. I’m not sure of the duration of the timer, but I think I have it set to 10x100uS (1mS).

// Timer Interrupt Handler
// Create a timed delay
void INTTIM()
{
    asm("
    di                   /* Disable interrupts             */
	add -4, r3           /* Increment sp by register size  */
	st.w r2, 0 [r3]      /* Store the contents of r2 in sp */
	movhi 0x0500, r0, r1 /* Put address of timer val in r1 */
	movea 0x0008, r1, r1 /*                                */
	ld.w 0 [r1], r2      /* Load timer value into r2       */
    add 1, r2            /* Increment timer value by 1     */
    st.w r2, 0 [r1]      /* Store timer value back in ram  */
    ld.w 0 [r3], r2      /* Retrieve previous r2 from sp   */
    add 4, r3            /* Set sp back to previous value  */
    ld.w 0 [r3], r1      /* Retrieve previous r1 from sp   */
    add 4, r3            /* Set sp back to previous value  */
    ei                   /* Re-enable interrrupts          */
    reti                 /* Return from interrupt          */
    ");
    
    return;
}

// Timer Initialisation
// Create a timed delay
void InitTimer()
{
    HW_REGS[THR] = 0x00; // THR, timer duration value high byte
    HW_REGS[TLR] = 0x09; // TLR, timer duration value low byte
    HW_REGS[TCR] = HW_REGS[TCR] & ~TIMER_20US; // T-Clk-Sel = 0, 100uS delay
    HW_REGS[TCR] = HW_REGS[TCR] | TIMER_INT;   // Tim-Z-Int = 1, enable interrupt
    HW_REGS[TCR] = HW_REGS[TCR] | TIMER_ENB;   // T-Enb = 1, turn on timer
    
    return;
}

Hope this is some help. I haven’t touched this since the early days (it was made just after the timer was figured out IIRC), so it probably doesn’t work anymore.

…Game engine?

Did I miss something?…

$50? You could have bought a copy of Jack Bros or Waterworld for that. >:(

…And $250? Wheres he buying it from? Toys ‘R’ Us way back in 1995? 😛

How would that work? Besides the eyeholes, the rest of the case is opaque.

I don’t have any dead VBs, however I would be interested in the internals (functional preferred) should you come across a complete unit. 😉

You’ve pretty much included all I’ve thought of over the years.

Only thing I can think of is releasing your code so we can all make custom skins/OSs. 😛

Excellent! 😀

With both our (and RunnerPack’s) sites offline, a lot of the little stuff that PVB doesn’t cover was unavailable.

I’ve worked a little on my site, but unfortunately I’ve run out of holidays and it may be even longer before I can get to work on it more. 🙁

Sounds good.

I also have to rely on DT’s prog doc.
I keep losing my IRC logs of VB stuff I’ve gained over the years. 🙁

This is a common problem.

Over time the glue holding the display cables to the board seems to separate.
DogP is offering a service to reglue the cables. There should be some threads about it somewhere on this forum.

I have a similar problem.

Not with the background image, but with the whole red screen thing (not that I don’t like it ;-)).
During the daytime I have to select the text to be able to see it.

4×2 for the link port, and a row each side to fit the port.

Just bought one of these.
I snapped it into a set of 6×2, trimmed the front corners slightly, and bent the (long) pins inwards.

It fits perfect! All the connections line up and it stays in all by itself.

…And best of all I can get 3(.333) connectors for $1.44AUD. 😀

No chopping AV/FDD/ISA plugs/sockets for me… 😉

Attachments:

1. 

   productlarge_1229.jpg