Afaik that still requires you to run in test-signing mode, 4wd.

Going by the instructions, you only need test mode if you want to then run your self-signed driver on another system which, (naturally), doesn't have the system certificate it was signed with.

Making Other Systems Accept the Signed Driver

Clearly this is a solution of limited value, as the only copy of 64-bit Windows that is happy with your app/driver now is the one that you just did the work on.  The signature on the driver only works there because makecert installed the root certificate for your driver signature in your local driver store.

To me that reads as if the resultant signed file will work on the signing system without requiring test mode.

But without actually having something to test it with -

BothXP Pro and W7 would only show 3gb usable, while showing I did indeed have 4gb of mem.
Some limitation with 32bit.

Depending on what hardware you have in your machine you are very unlikely to see more than 3.3Gb of RAM in a 32 bit system and if your grapgics card has large onboard memory you are likely to see less than that (which probably accounts for the the 3Gb only). Vista and 7 do recognise that you have 4Gb available but the way it works is that any devices with mapped memory (eg. graphics cards) is removed from your 4Gb so that it can be mapped.

If Windows 7 32-bit is blue screening and the memory is OK I would guess it is a driver issue. I am starting to come across a number of systems (32 and 64 bit) that are having issues with drivers installing out of the box. This includes my own desktop system - I tried to install 7 and Vista, both 32-bit and 64-bit and all 4 versions blue screened. My motherboard is Vista certified and my graphics card is identical to one I use on another machine with windows 7 so I suspect it is another piece of hardware present in my desktop box that is causing the problem At the moment I can't be bothered to fix it but when I get round to it I will need to remove all inessential hardware before the install and then add them back bit by bit and download the relevant drivers from the manufacturer because obviously something doesn't like the drivers supplied by MS during Windows setup.

Yes Carol, I hear ya.
Investigated all that the best I could.
The thing is it worked fine with only 2gb of memory, but when you go over that, it throws a hissy.
I have 512 nvidia 8600 graphics card.

It just seems a bit crazy, all that mapping stuff, to me anyway.
When the card has it's own memory....

I read another thread on it here at DC and a bunch of other sites.

edit-

Since this is a W7 upgrade disk, it will not activate or even install fully unless I have XP up and running.
So I have to install XP first then upgrade to W7 if I want to try.
XP is on right now, and it takes a while, like 2 days to get it fully loaded.
A 2005 disk needs a lot of updates and removing the ton of included extra programs.
The darn thing has norton, mcafee, aol and some other unwanted, not needed, outdated stuff.

Probably needs a bios update, yes.
I'm not confident to do it though.
The chances of turning it into a door stop.

what does this mean?

In particular make sure your memory settings are conservative.

Something about the memory mhz or overclocking?
Used the same type of memory/mhz it came with.

edit-gotta go to work ttyl

Probably needs a bios update, yes.
I'm not confident to do it though.
The chances of turning it into a door stop.

The important points to BIOS updating are:

1) Be 100% certain that you download the correct BIOS update for your motherboard direct from the manufacturer's website. Model numbers are always printed on the motherboard somewhere (often between the expansion slots - you may need a torch!). However, if it is a factory built computer system from a big box shifting manufacturer don't rely on the printed model number on the motherboard as manufacturer's often buy cheaper modified versions of motherboards and supply limited BIOS options - you then can't 100% guarantee that the BIOS from the motherboard manufacturer is completely compatible  (though I have to say I have used this method to release previously unavailable BIOS options and never had a doorstop at the end - but you should be aware of the issue).

2) If you are happy to upgrade the BIOS follow the manufacturer's instructions to the letter

3) If things seem to take longer than expected don't be tempted to do anything silly (such as press the OFF button or reset) go and get a strong drink and come back later.

Having said all that I agree with steeladept - I have performed more BIOS updates than I can remember and have never (touch wood) killed a motherboard yet by doing so.

Your current BIOS seems to have been superseded by 4 versions. Try the top one (5/2/2007) which is designed to add support for Vista (and by implication it is the one most likely to be best with Windows 7).

Windows 7 should install the correct drivers for the motherboard automatically but it cannot hurt to download the latest versions and have them ready. The motherboard driver listed there is ancient - try using something like Speccy or SIW to correctly identify the motherboard and look on the chipmaker's website for the most recent version with Windows Vista/7 support (from the images above it looks like it is an Intel chipset).

Speccy: http://www.piriform.com/speccy/builds (use the portable version)
SIW: http://www.gtopala.com/siw-download.html (go for the free version without installer)

Once you have found out which chipset you can look for a driver here:

http://downloadcenter.intel.com/Default.aspx?lang=eng

Bios update worked! Easier then I thought, thanks.
It actually flashed it twice cause it was so old,
and stated that may happen in the instructions,
which I followed.

The other computer I flashed, I had to from the 3.5 disk.
Yeah a long time ago.
It's been while and I couldn't remember if it kept the OS, which it did.
Still reading only 3gb memory, but normal, right?

Not ready to do W7 yet, I think I'll make a full backup first.
So I don't have to start from scratch again for XP if needed.

W7 had trouble with my tv tuner card (ati), working for a bit then loosing the tuner's signal.
Works fine with XP media center installed, glad I had called for that disk long ago.

I use an ATI tuner card with Windows 7 & it works great. I record stuff off of cable all the time....when I remember I have a tuner card in my PC! I went so many years without one I often forget it's there.

Progress update-

Looks like the bios update is what was needed.
Got lost in Intel's site, so I'll let W7 figure it out.
No blue Screens, still 3gb usable memory.
Thanks to all and especially Carol.
(btw, what did you use to adjust my uploaded pics for better viewing in that post, Carol)

Dual booting right now with XP and W7, plus a backup of XP.
I haven't checked everything yet as it is still updating.
I just loaded it earlier today and I know there will be some more updates, before I start loading what I want on W7.
I expect I'll go back to full W7 again, not sure, XP doesn't take much room but still needs to be booted into from time to time to keep it updated.

Thanks again,
Clay

Well done - glad you got it working.

To insert image use the drop down on the left (Link Inline Image ...) so the article I edited became this:

Thanks for the replies and help.
I have considered updating the bios.
I've done it once on anther machine successfully.

Here's what I'm looking at from gateway support.
Which doesn't seem updated enough.

This is after input of my computer serial number,
and scanning current configuration, with available downloads.
So these are for this Computer.

[attachthumb=1]

[attachthumb=2]

[attachthumb=3]

The 1,2,3 refer to the order in which the images were attached to the message.