Recent content by OzzFan

I'm all ethernet here. My legacy devices use 10Mbit and my modern devices use 1Gbit or WiFi ax. My newer servers are all connected via 10Gbit fiber via a Unifi 10Gbit switch. My router is Unifi and my two 24 port gigabit switches are Cisco small business. Nice and simple.

You're right. Thanks for the correction. Given those numbers, 320MB/s + 125MB/s is under the 512MB/s of the 64-bit 66MHz PCI-X bus. I guess it would be difficult to saturate that bus.

Early PCI-X chipsets, including most Pentium III class boards only supported 64bit 66MHz speeds which maxes out around 512MB/s. 1Gb ethernet consumes about 12.5MB/s, and full duplex SCSI U320 will consume 640MB/s theoretically.

The chipset is just the glue logic that handles stuff like memory I/O, access to expansion slots, onboard devices, etc. This is separate from whether or not the OS supports dual processors. Both the chipset and the OS must support dual processors in order to work properly. ServerWorks became...

Small correction: I'm using Symantec C++ 7.2. Yes, Symantec has the MK_FP macro, but it does not support the huge memory model, but it does support large and far. I'll have to play around with MK_FP to see if I can get it to work.

Anyone have any tips on reading ROM strings from DOS? Specifically I'm trying to locate the video ROM BIOS string from C000:0 and the computer ROM BIOS string from F000:0. Is there an easy way to do this? I tried writing a loop variable with a list of common strings to search for, but my...

I try to make it a point to run a different OS on most of my collection, and I try to make it period correct if I can. For example, I run standard MS-DOS 5 on my 386DX; OS/2 2.11 on my IBM PS/2 56SX, OS/2 3 Warp Connect on my IBM PS/2 model 77, PC DOS 7 on my Cyrix Cx5x86 100MHz. I had IBM...

The site seems to be working on my Windows 95B machine, and I was able to download some updates for my NT 4.0 Server system as well. I haven't tested it with my various other OSes yet, but I'm really liking it so far. Various updates did complain on my NT 4 Server that they weren't appropriate...

AUTO95.EXE is a simple program I wrote to streamline the Windows 3.1x to Windows 95 retail upgrade process. The application will scan your removable and networked drives, as well as the current working directory for the Windows 95 source files, then copy them to \CABS95 under your Windows...

I thought it was the other way around: PPGA had the core facing downward and FCPGA (literally an acronym for "flip chip pin grid array" with the core being "flipped" over) with the core facing upward to allow for better heat transfer with the CPU heat sink & fan assembly.

I'm happy with my ATi Mach64-based ISA card. It performs well enough for some really old DOS games like One Must Fall: 2097 and DOOM, but I'm using an Am5x86 133MHz chip. It may not be the speediest, but it is far better than the onboard OAK VGA that the system has.

I was able to figure out how to get the state of the radio buttons by using SendDlgItemMessage() like so: BOOL CALLBACK MainDlgProc( HWND hDlg, UINT Message, WPARAM wParam, LPARAM lParam ) { switch( Message ) { case WM_INITDIALOG: return TRUE; case WM_COMMAND...

I had an 'OK' Command Button in the dialog box to be clicked after selecting the radio button but I still couldn't figure out a way to determine which radio button was selected after pressing OK. I guess that's the part I'm struggling with.

I gave that a try and only the same behavior resulted: only the restore radio button worked as before. I also added a break statement per your suggestion but that didn't do anything. This at least tells me that whatever wParam is returning, it is equal to IDB_RESTORE and never equal to...

No, I simply missed that when retyping it. Thanks for pointing that out though! I edited my original post to fix it.