For quick reference:

OEMINFO.INI wrote:

[…]
Show full quote

Copy code to clipboard

1[general]
2Manufacturer=Company Name
3Model=Custom
4
5[Support Information]
6Line1=" For technical support and service,"
7Line2=" buy a new computer."

Your logo image, at least in Win9X, 2K, and XP, should be 180x114, and 8 bit color if you want transparency. Palette index 0 will be your transparent color. If you use Paint Shop Pro to create and edit your logo, you can change palette settings under Colors, Edit Palette (in in PSP X, Image, Palette, Edit Palette). Double-click palette index 0 and change it to a color not used in your image. I usually use bright green (#00FF00) or bright purple (#FF00FF). The filenames I use for my images are:
9X: oemlogo.bmp
2K: oemlogo-2k.bmp
XP: oemlogo-xp.bmp
The batch file below handles renaming the files after they've been copied to the appropriate directory. This just allows you to use different images for different Windows Versions, so you can make era-appropriate logos, if that's your fancy.

And for easy-peasy installation of your custom logo and information:

OEM.BAT wrote:

[…]
Show full quote

Copy code to clipboard

1echo off
2copy oemlogo.bmp %systemroot%\system32
3rem ***************************************************
4rem Script for deploying OEM INFO and OEM LOGO to
5rem different operating systems
6rem Simon Butler, Amset IT Solutions Ltd. 12-12-03
7rem see http://www.amset.info/netadmin/oemlogo.asp
8rem Requirements
9rem Image file for Windows 2000 named oemlogo-2k.bmp
10rem Image file for Windows XP named oemlogo-xp.bmp
11rem And oeminfo.ini file.
12rem
13rem All three files should be placed in the same
14rem directory as this batch file
15rem If running from login script, place all three files
16rem in your "netlogon" share on the domain controllers.
17rem Remember - if you are running from a network share
18rem it must be a mapped drive!
19rem ***************************************************
20
21rem Get the OS and dump to file
22ver >%systemdrive%\ver.txt
23
24Rem now find the operating system and act accordingly
25findstr "4.0" %systemdrive%\ver.txt
26if not errorlevel 1 goto nt4
27findstr "5.0" %systemdrive%\ver.txt
28if not errorlevel 1 goto win2k
29findstr "5.1" %systemdrive%\ver.txt
30if not errorlevel 1 goto winxp
31findstr "5.2" %systemdrive%\ver.txt
32if not errorlevel 1 goto win2003
33
34goto win9x
35
36:nt4
37set OpSys-NT4
38echo %OpSys% >>%systemdrive%\result.txt
39rem Windows NT4 settings
40
41copy oeminfo.ini "%systemroot%\system32"
42copy oemlogo-2k.bmp "%systemroot%\system32"
43del "%systemroot%\system32"\oemlogo.bmp
44rename "%systemroot%\system32\oemlogo-2k.bmp" oemlogo.bmp"
45
46goto next
47
48:win2k
49set OpSys=Win2K
50echo %OpSys% >>%systemdrive%\result.txt
51rem Windows 2000 settings
52
53copy oeminfo.ini "%systemroot%\system32"
54copy oemlogo-2k.bmp "%systemroot%\system32"
55del "%systemroot%\system32"\oemlogo.bmp
56rename "%systemroot%\system32\oemlogo-2k.bmp" oemlogo.bmp"
57
58goto next
59
60:winxp

…Show last 43 lines

61set OpSys=XP
62echo %OpSys% >>%systemdrive%\result.txt
63rem Windows XP settings
64
65copy oeminfo.ini "%systemroot%\system32"
66copy oemlogo-xp.bmp "%systemroot%\system32"
67del "%systemroot%\system32"\oemlogo.bmp
68rename "%systemroot%\system32\oemlogo-xp.bmp" oemlogo.bmp"
69
70goto next
71
72:win2003
73set OpSys=Win2003
74echo %OpSys% >>%systemdrive%\result.txt
75rem Windows 2003 settings
76
77copy oeminfo.ini "%systemroot%\system32"
78copy oemlogo-xp.bmp "%systemroot%\system32"
79del "%systemroot%\system32"\oemlogo.bmp
80rename "%systemroot%\system32\oemlogo-xp.bmp" oemlogo.bmp"
81
82goto next
83
84:win9x
85set OpSys=9x
86echo %OpSys% >>%systemdrive%\result.txt
87rem Windows 9x settings
88
89copy oeminfo.ini "%systemroot%\system32\"
90copy oemlogo-2k.bmp "%systemroot%\system32\"
91del "%systemroot%\system"\oemlogo.bmp
92rename "%systemroot%\system\oemlogo-2k.bmp" oemlogo.bmp"
93
94goto next
95
96:next
97echo done >>%systemdrive%\result.txt
98echo Cleaning up!
99del %systemdrive%\result.txt
100del %systemdrive%\ver.txt
101rem if problems, put REM in front of above two lines
102rem to read the results files.

Put all of these on a floppy or flash drive, insert, and run the batch file.

I'm almost done with my hard disk plexiglass thing!

https://youtu.be/lTxyFkq1r9k

It was hot upstairs so I reorganized some stuff down in the retro room. Decided to hook up my MSX2 system and verify it was still working (been a few years). It still showed the correct date! But it had a 1.4GB HDD connected to a Sunrise IDE cartridge. I had to smack it a few times to get it to spin up, and then some files wouldn't read so I guess it's dying. Time to salvage some data while I still can (of course I probably have all the same files on my PC somewhere)

I found a virus on a diskette I installed a game onto a client from.

Naturally, 400+ diskettes were scanned today.

Then I organized them, why not, from this lot:

to this lot:

I took the opportunity to format a handful of diskettes and put them in the "to use" pile while I was at it.

Certified <2006 virus free!

Jed118 wrote:

I found a virus on a diskette I installed a game onto a client from. […]
Show full quote

I found a virus on a diskette I installed a game onto a client from.

Naturally, 400+ diskettes were scanned today.

Then I organized them, why not, from this lot:

to this lot:

I took the opportunity to format a handful of diskettes and put them in the "to use" pile while I was at it.

Certified <2006 virus free!

What type of virus that would be found on a floppy would be any sort of threat today?

TheAbandonwareGuy wrote:

What type of virus that would be found on a floppy would be any sort of threat today?

It certainly is if you use this floppy on a vintage machine with an older OS!

ThinkPad 770x w/ SelectaDock II
300Mhz P II
512 Ram
Trident 975 8MB
440BX Laptop 🤣

SB64G, Voodoo2,Intell 100s Installed in the Dock

IBM DEVA Mpeg2 Decoder + IBMVCAP Only 30% CPU utilization on Pentium 2 300 MHZ

MDK Performance

What executable do you use for MDK with voodoo 2 ? The only 3dfx patch I can find only works right with a voodoo 1

MDK 3DFX VOODOO2 working
http://www.mediafire.com/file/6nyan5pcpnkoout … 363d17.zip/file

and not sure if it makes a difference I was also using
3D Control Center V1.0
(Direct3D control & switching Utility)
https://3dfxarchive.com/downloads/3dcc.zip

Went on a 3 hour train ride to buy a 3DFX Voodoo 3 3000 with a BLACK HEATSINK. I'm so fking happy right now.

Sorta retro activity related.

I had a really trashed PCChips motherboard box that I was going to throw out.

Then I was working on my John Deere 285 Lawn tractor and needed a gasket fore the oil filler tube.

Noticed that the top layer of the corrugated cardboard for the PCChips box was the perfect thickness for the gasket so I made myself a gasket instead of having to wait at least 2 business days to be able to get one if I ordered it. Just enough silicone glue to make a super thin layer on each side of the gasket when installing and it is as good or better than a stock gasket.

Got a new XP rig test booted and partially built.. bought the motherboard as broken, found out that the only problem was a dead CMOS battery. Other than that, it looks brand new. Weird that it wouldn't boot with a dead CMOS battery. Might have been due to not being able to save memory timing/voltages because it kept throwing the bad memory beep code with everything I put in it.

Specs:
ECS KN1 Extreme
AMD Athlon64 FX-57
Thermaltake Big Typhoon CL-P0114
2GB (4x512MB) Crucial Ballistix Tracer DDR500/PC4000/CL2.5
Nvidia GeForce 7800GTX
Coolermaster Mystique "Xoxide/Kikboxes High Roller Case" I won off an Xoxide contest

Next up:
- Install WD Raptor X
- Install DVD-ROM
- Sound card, maybe (DMX6fire or SB Audigy2 ZS)
- Install Windows XP

wiretap wrote:

Got a new XP rig test booted and partially built.. bought the motherboard as broken, found out that the only problem was a dead […]
Show full quote

Got a new XP rig test booted and partially built.. bought the motherboard as broken, found out that the only problem was a dead CMOS battery. Other than that, it looks brand new. Weird that it wouldn't boot with a dead CMOS battery. Might have been due to not being able to save memory timing/voltages because it kept throwing the bad memory beep code with everything I put in it.

Specs:
ECS KN1 Extreme
AMD Athlon64 FX-57
Thermaltake Big Typhoon CL-P0114
2GB (4x512MB) Crucial Ballistix Tracer DDR500/PC4000/CL2.5
Nvidia GeForce 7800GTX
Coolermaster Mystique "Xoxide/Kikboxes High Roller Case" I won off an Xoxide contest

Next up:
- Install WD Raptor X
- Install DVD-ROM
- Sound card, maybe (DMX6fire or SB Audigy2 ZS)
- Install Windows XP

What sense would a TerraTec DMX card make for gaming? An X-FI would make much more sense for a build from that era.

I finished making this screen bezel for my portable PC case:

There's more pictures in the thread:
LCD Portable PC clone, display replacement

TheAbandonwareGuy wrote:

What sense would a TerraTec DMX card make for gaming? An X-FI would make much more sense for a build from that era.

I don't believe I said it would be used for gaming. I had some other uses planned for it, such as audio/video work - I mentioned the TerraTec card and Audigy2 ZS since I have those on hand with convenient front I/O panels.

Cleaned all 14 of my Nintendo 64 game cartridges with DeoxIt and cotton swabs (Q-tips) and the console itself (cartridge slot and left controller ports). I also oiled the heatsink fan for the Socket 5 build a fellow Vogoner sent to me.

Planning on replacing the left controller ports, the cartridge slot, and the casing as it's been broken for a long time. Might do an RGB mod on it.

Trying to get this new retro setup going... out of ideas on why it won't POST with the Corsair HX1000 but works just fine with this ancient VPower 400w hunk-o-junk.

The HX1000 probably doesn't have enough 5 Volt power for it. The Vpower 400W hunk of junk is probably a 3.3V/5V focused PSU, which is why it can handle it better.

canthearu wrote:

The HX1000 probably doesn't have enough 5 Volt power for it. The Vpower 400W hunk of junk is probably a 3.3V/5V focused PSU, which is why it can handle it better.

I thought that as well, but after looking at the numbers I don't think that's the problem...

There are 4 pins in the 20 pin ATX connector which are +5v, and each pin per spec is only rated for 6A, so 24A of +5v total. This VPower LC-B400ATX has 28A on +3.3v, 40A on +5v, and 17A on +12v rails while the Corsair HX1000 has 30A on +3.3v, 30A on +5v and 100A on +12v.

Given that the VPower has 10A more on its 5v rail I also assumed that to be the reason, though pulling over 30A just to boot up seemed a bit outlandish (I was trying with only the CPUs, 1 RAM stick and an AGP card installed).

However... since 24A is the max possible to pull over the 20 pin ATX connector, I am fairly certain that lacking amps on the 5v rail is not the problem.

kalm_traveler wrote:

I thought that as well, but after looking at the numbers I don't think that's the problem... […]
Show full quote

canthearu wrote:

The HX1000 probably doesn't have enough 5 Volt power for it. The Vpower 400W hunk of junk is probably a 3.3V/5V focused PSU, which is why it can handle it better.

I thought that as well, but after looking at the numbers I don't think that's the problem...

There are 4 pins in the 20 pin ATX connector which are +5v, and each pin per spec is only rated for 6A, so 24A of +5v total. This VPower LC-B400ATX has 28A on +3.3v, 40A on +5v, and 17A on +12v rails while the Corsair HX1000 has 30A on +3.3v, 30A on +5v and 100A on +12v.

Given that the VPower has 10A more on its 5v rail I also assumed that to be the reason, though pulling over 30A just to boot up seemed a bit outlandish (I was trying with only the CPUs, 1 RAM stick and an AGP card installed).

However... since 24A is the max possible to pull over the 20 pin ATX connector, I am fairly certain that lacking amps on the 5v rail is not the problem.

Could also be with the giant distance of ATX specs. Like say for example. . .1.3 vs 2.0 or something. The way the PSU delivers power may have something to do with it, like the 12v rail not getting enough usage.