Actually, it was never finished because Alberto couldn’t get his flash cart working.

I don’t think the way he was planning to do it would have been that limited by the link port. I think he was (is?) going to use the VB as a “GPU” like those in modern video cards. (And sound too, I assume. Maybe even the controller, though it’s not one of the better ones, IMHO…) so only elements of the display would have to be transferred, which the VB would then render, rather than screen-sized bitmaps. Also, compression isn’t completely out of the question. But, since it needs a cart to boot the VB, anyway, an Expansion-based link would be viable, too.

But, assuming you actually like the VB’s display (does anyone? :-P) it would be better to make a new “video card” for it and leave the VB’s CPU/GPU out of the equation.

The patent has pretty much everything one would need to know (except the pinouts, which can be found through experimentation) including the method used to make different shades of red (which could, of course, be expanded to include more shades by the adapter.)

So… How much would anyone be willing to pay for such a thing?

Hey, where are the links!?!?!?

That’s really weird… Anyway, you can search by the names above and probably find them. I’ll leave them up as long as possible, and I can send them directly, if you use an IRC client with DCC capabilities and log on to EFnet #virtualboy

I would also vote for using the interrupt, but another way would be to actually control the VB’s power source (i.e. perform a “cold reboot.”)

This can be done one of two ways: (Without modifying the VB or keypad…)

1. Put a relay, power transistor, or other switch in series with the (6 to 15 VDC) power source going to or coming from the keypad.

2. (This will require testing) Connecting +5 VDC to one or more of the Vcc lines on the cart socket should power the rest of the VB, basically bypassing it’s voltage regulator. (Be sure you DO NOT put batteries or an adapter in the keypad, of course! ;-)) If so, you could then control this source as in option #1.

Of course, by modifying the VB, there are a number of ways it could be done. You could even change pin 5 into an actual /RESET line.

HTH,
Amos

It’s probably also made much easier than x86 by the fact that the v810 is a RISC chip.

(I’ve probably mentioned this before, but…) I want to make something like Brian Provinciano’s NES assembler for the VB. It has shortcuts and aliases for common programming structures and NES hardware ports.

Sorry…

I removed the self-extract module from the one above (it may still have sources, though *shrug*)

Here are some new links:

WinX3D HWI Setup 3.20 NT.rar

WinX3D Setup 3.20 95-98-Me.rar

WinX3D Setup 4.17 NT-2000-XP.rar

And, a WinX3D-based video player (haven’t tested it)

Winx3d_video_beta8.zip

Congrats on the HMD, BTW! What’s the make/model? Where’d you get it? How much?

I’m this close to getting an Nvidia card. Apparantly, they’re the best cards for “depth-heads” like us

If you find the WinX3D SDK, be sure let me know!

Okay, I now have 3 versions of WinX3D. But, to actually use it, I need the SDK so I can write some software, since there’s NOTHING OUT THERE THAT USES IT!!! :/

The worst part is that I had both the drivers and the SDK at one time! Now that I have shutter-glasses, NOTHING!

AAAAAARGH!!!!

Sorry… I’m okay, now.

Maybe I can reverse-engineer an SDK…

I think it depends on your locale, but it’s probably safe to assume emulators themselves are perfectly legal.

The only thing about emulation that’s illegal (to my knowledge) is the distribution of copyrighted software (i.e. “ROMs.”) Although, use of certain information in making the emulator (such as violation of NDA’s, etc.) might get an emulator author in trouble…

But, as long as you only play public domain ROM images, (and, of course, those created by yourself) you should be fine.

Note:

By reading this message, you agree to the following terms:

Amos J. Bieler (“the Author”) hereby disclaims all responsibility for any legal action taken upon anyone else (“the Reader”) due to the use of, or inability to use, the contents of this forum post (“the Document.”)

This message copyright (C) 2005 Amos J. Bieler. All rights reserved.

YES! I finally found a copy of the 2000/XP version on emule! I’d still like a copy of 98, though… Maybe someone has it to trade?

Here’s an ed2k link. I’ll probably leave it up for quite a while.

[u]ed2k://|file|WINx3D-2000-XP-Setup.exe|2366175|B4D1BB1A7EC9C8F99C13F29F04B08B3C|h=ZZP7Z37IEPPXBZ5AJ7BMJQGXCUMI3KTL|/|sources,12.226.172.51:6699|/[/u]

First, welcome to the forum! :vbsmile:

:question: 1. Do you think it would help you find out more if all us fans signed a petition of some sort?

(You could whip up a quick one for the site, right KR155E?)

I’d sign in a heart-beat, even if it wouldn’t.

:question: 2. What do you think about a few of us amateur coders taking your version of the script and screen-shots of the game and making a new version?

:question: 3. Did you ever play it? If so, for how long? (As in, “off-and-on” vs. “for long stretches”.)

:question: 4. How many other VB developers do you know that are still fans of (or even just still like) the VB?

Thanks! And good luck finding a copy!

I’ve tested the latest Reality Boy and interlaced mode works good, but…

Since the lines are interlaced, but the pixels aren’t doubled horizontally, everything is stretched and looks taller.

Just needs the horizontal bits of the scaling code sorta massaged into the interlaced code

Para: is the VB really 50 fps for both eyes, or is it 50 total, divided between the two? (Like the 50 “fields” per sec. of PAL) I know it scans the screens one at a time, but I don’t know what the actual mirror oscillation rate is… Anyone have an open VB and a calibrated strobe light?

(Can’t edit posts anymore :-()

Note, while I still would like a copy of ESL, now I’m also looking for copies of the WINx3D drivers (for both 9x and XP/2K) and something called “VRCaddy”.

The makers of both seem to be defunct, and I can’t find them on the usual p2p sources.

I’ll also take anything else related to shutter-glasses, especially “H3D,” “e-Dimensional,” and things using interlaced video modes.

Thanks

WOOOOOOOOOOOOOOOOOOOOOOOOOOOT!!!!!!!

They finally (stupid USPS >:() arrived yesterday and they SUPER-TOTALLY-HARD-CORE-ROCK-THE-FREAKIN-WORLD!!!!!

It turns out it was actually the wireless set (seller was mistaken) but there’s a port for the wired glasses, too. So, I can use both pairs at once, and I don’t even need the splitter!

If I use them at 85Hz, the only flicker is in the stuff in the room, like my monitor bezel. A dark room fixes that. At 120Hz (limited to 640×480 mode on my _current_ system ;-)) there is absolutely no flicker AT ALL!

Plus, the glasses are turned on and off by a simple set of colored lines on the top few rows of the screen. They sorta look like a stretched out German flag, cause they use horizontal stripes of red, yellow, black (and green). These could be easily incorporated into RB/RD/VUE32.

Well, enough typing… THERE’S 3-D TO SEE!!!!

You’re, of course, entitled to your opinion. But, both the fact that you like Vexx and your poor spelling skills, show your lack of intelligence.

You should also refrain from cluttering up topics with childish, mean-spirited outbursts, and then agreeing with yourself like the loser you are.

Back on-topic: I’m trying/playing (depending on quality ;-)) a bunch of SNES games I never bothered to try when they came out; “Krusty’s Super Fun-house” and “Pushover” to name but two.

D’OH! I completely failed to mention that I got them on eBay and they haven’t arrived yet

I’ll let you know what it’s like when I get them all set up…

Oops… It looks like you had the left/right swapped when you took the shots. If the check-box for “Swap 3D” in RD is checked, clear it. (If it’s clear, check it.)

Or, you could just reverse the names given during whatever process you use to separate the images. And, of course, rename the files you already have appropriately…

Good job, though! Looks sweet! Can’t wait to see PVB3 up and running!

He has, just not in a very visible location…

This article by DogP has a description of his screwdriver modification in it.

So… When/where can we see some shots?

You should ask the developer. Maybe you can’t change those things at runtime, or you have to call a “refresh” function of some type…

I’d leave the memory out of the device itself and just make hw that sends the video data directly to the PC, which could then render and/or store it. Just my $0.02…

For those that don’t know, the screen interface is something like a series of (28?) NES pads. Groups of 8 “pixels” (enough for every row in the 224 pixel tall screen) are each “shifted” over a wire and all synchronized to a clock pulse. Both screens are connected to a common “bus” and activated by a “select” signal. Only one screen is drawn at a time.

The hard part about decoding the data is the fact that the shades are done with PWM. The ratio of a pixel’s on and off times determines how bright it is. This is further complicated by the “column tables” that correct for the “pendulum” motion of the mirrors. That’s why I think it should be left to the PC.

1. RBF crashes as soon as it’s run, before it even makes a window.

2. I’m running Win98 and have only FAT32 partitions, so no “permissions” at all.

3. RBF compiles fine with VC++6 (Visual Studio 6) but the resulting executable crashes identically to the distributed one.

Your binary:

RBOY_FRONT caused a stack fault in module RBOY_FRONT.EXE at 0187:00401287.
Registers:
EAX=040003eb CS=0187 EIP=00401287 EFLGS=00010246
EBX=00542060 SS=018f ESP=00542000 EBP=0054202c
ECX=00000000 DS=018f ESI=00008084 FS=29a7
EDX=000009b8 ES=018f EDI=00542014 GS=77df
Bytes at CS:EIP:
68 eb 03 00 00 52 ff 15 ec 90 40 00 5f c6 05 d8
Stack dump:
00000000 00000000 00542014 00008084 bff7363b 000009b8 00000111 040003eb
000009fc 805e7837 0000018f 00542040 bff94407 77df8084 000077df 00000000

My binary:

RBOY_FRONT caused a stack fault in module RBOY_FRONT.EXE at 0187:00401287.
Registers:
EAX=040003eb CS=0187 EIP=00401287 EFLGS=00010246
EBX=00542060 SS=018f ESP=00542000 EBP=0054202c
ECX=00000000 DS=018f ESI=00008084 FS=a09f
EDX=00000768 ES=018f EDI=00542014 GS=cc7f
Bytes at CS:EIP:
68 eb 03 00 00 52 ff 15 e4 80 40 00 5f c6 05 bc
Stack dump:
00000000 00000000 00542014 00008084 bff7363b 00000768 00000111 040003eb
000007d0 805eccd7 0000018f 00542040 bff94407 cc7f8084 0000cc7f 00000000

BTW, I got rid of the compiler warnings about converting long to bool. I just changed all the bool casts into an equality test. The “patched” code starts around line 135:

		case IDC_SWP_CHECK:
			s.swap = (SendMessage ((HWND) lParam, BM_GETCHECK, 0, 0) == BST_CHECKED);
			break;
		case IDC_LTHACK_CHECK:
			s.timmerHack = (SendMessage ((HWND) lParam, BM_GETCHECK, 0, 0) == BST_CHECKED);
			break;
		case IDC_VFHACK_CHECK:
			s.vfHack = (SendMessage ((HWND) lParam, BM_GETCHECK, 0, 0) == BST_CHECKED);
			break;
		case IDC_DBG_CHECK:
			s.debug = (SendMessage ((HWND) lParam, BM_GETCHECK, 0, 0) == BST_CHECKED);
			break;

		case IDC_THR_CHECK:
			s.nothrtl = (SendMessage ((HWND) lParam, BM_GETCHECK, 0, 0) == BST_CHECKED);
			break;
		case IDC_STS_CHECK:
			s.status = (SendMessage ((HWND) lParam, BM_GETCHECK, 0, 0) == BST_CHECKED);
			break;
		case IDC_DIS_CHECK:
			s.disasm = (SendMessage ((HWND) lParam, BM_GETCHECK, 0, 0) == BST_CHECKED);
			break;

		case IDC_CON_CHECK:
			s.stdOut = (SendMessage ((HWND) lParam, BM_GETCHECK, 0, 0) == BST_CHECKED);
			break;

4. I haven’t tested much because my ROMs are RAR’d to save space… (Better ratio than PKZIP.) I’m going to see if I get good ratios with 7zip, since the extraction library for those is OSS and does PKZIP, as well.

P.S. Congratulations on the birth of your daughter! :thumbsup: