1. Found New Hardware Wizard. Click NEXT

2. What do you want the Wizard to do? Select the option:
   Display a list of the known drivers so that I can choose a specific driver.

3. Click on Next, select MODEMS from the list and click Next again.

4. Select Rockwell from the Manufactures list, and then select your Model corresponding to the list below.
   Boca models: Rockwell Driver:
   M56IV Rockwell Compatible Internal V90, K56Flex, Voice, Speakerphone
   MD56IV Rockwell Compatible Internal V90, K56Flex, Voice, Speakerphone

   M56EV Rockwell 56K Data Fax Voice Modem (RCV56ACF)
   MD56EV Rockwell 56K Data Fax Voice Modem (RCV56ACF)

   M56I Rockwell DPF (PnP)
   MD56I Rockwell DPF (PnP)

   M56E Rockwell DPF External Modem
   MD56E Rockwell DPF External Modem

   MDDL56I Rockwell DPF (PnP)

5. Click on Next, it will display an Update Driver Warning, click on YES

6. Click on Next again and Finish.

AT&F&C1&D2&K3\N0%C0

1. Your dialing location must be located within 3.5 miles of your local phone company's switching office. Even if you are WITHIN 3.5 miles of the switching office, you may or may not achieve 56K-range connect speeds -- but you certainly never will being over 3.5 miles from the switching office.

2. The phone lines in your dialing area should not be multiplexed by the local phone company.

3. If you have over a certain degree of line noise on your phone lines (i.e., line noise as it affects data calls, not voice calls {voice calls are notably less sensitive to being hindered by line noise than data calls are), this will cut back what connect speeds you achieve. Higher-speed connections are more affected by line noise than lower-speed connections.

4. There could be server problems or other issues on your ISP's end (i.e., it could be the firmware version that the ISP is using, it could be server setup problems or malfunctions on their end, it is could be that the ISP's servers respond better to certain modem chipsets (Rockwell/Conexant vs. Lucent vs. Texas Instruments [TI]) than other chipsets).

5. Problems with phone company lines or switches or other equipment (coming in or out of your dialing location or in nearby switchboxes or junctions or at their switching office, which serves your dialing location).

6. Of course, depending on what 56K protocols your modem supports (K56Flex-only, X2-only, Dualmode K56Flex-V.90, Dualmode X2-V.90, or V.90-only). We have only made K56Flex-only modems (which can be flash-upgraded to become V.90-only modems) or Dualmode K56Flex-V.90 modems (which handle both protocols). Dialing into an X2-only or V.34 server with your modem will not achieve any faster than 33.6 and, if your ISP supports V.90 but there are problems with your ISP's implementation of V.90 and they have Dualmode X2-V.90 servers, the modem can't fallback on K56Flex mode (being that the ISP's server is not Dualmode K56Flex-V.90 but rather Dualmode X2-V.90) -- so the modem will have no choice but to fallback to V.34 or lower rates. Then Rockwell/Conexant-chipset Dualmode modems (depending upon when you got your modem or if you are using the latest driver and firmware or not), by default, first tried to connect in K56Flex mode before V.90 mode (so if the ISP's servers did not support K56Flex, then such modems have no choice but to connect at V.34 or lower rates -- even your the other environmental factors were favorable to getting 56K-range connections); if your ISP doesn't support K56Flex but supports V.90, you have to explicitly tell the modem to operate in V.90 mode to have any chance of achieving 56K-range connect speeds. Then Lucent-chipset Dualmode modems, by default, first try to connect in V.90 mode and then K56Flex mode (so if the ISP's servers do not support V.90 but are X2-only, the modem will have no choice but to fallback to V.34 or lower rates; or if they support V.90 but there are problems with your ISP's implementation of V.90 and they have Dualmode X2-V.90 servers, such servers do not support K56flex, so the modem can't use K56Flex mode with such a server and therefore the modem will have no choice but to fallback to V.34 or lower rates -- even your the other environmental factors were favorable to getting 56K-range connections). If your ISP doesn't support V.90 but supports K56Flex, you have to explicitly tell the modem to operate in K56Flex mode to have any chance of achieving 56K-range connect speeds.

7. If the modem's signal has to pass through two or more analog-to-digital conversions at your phone company's central switching office, this will defeat achievability of 56K-range connect speeds.

1. Edit the SYSTEM.INI and remove the following lines from it:
   From the [Drivers] section:
   MSVIDEO=h20capt.dll
   VIDC.CYUV=yuvcodec.dll
   VIDC.i420=420codec.dll

   From the [386Enh] section:
   DEVICE=vdmamemd.vxd

   From the [VDMAMenD] section:
   NumberOfPages=256

2. Delete the following files ( the best way to do this is by clicking on Start > Find > Files or Folders ) ( Make sure that the customer is "Showing all files" by double clicking on My Computer then click on View on the menu bar and select Options. Then click on the View tab and make sure that the "Show All Files" radio button is selected and the "Hide MS-DOS file extensions for file types that are registered" checkbox is not checked.
   h20drv.dll
   h20capt.dll
   h20.ini
   ctdmamem.dll
   vdmamemd.vxd
   eyeway.dll
   audway16.dll
   audway32.dll
   420codec.dll
   yuvcodec.dll
   eyeway95.inf
   Make sure you also delete the OEMx.INF that is copied to the INF directory.
   This whole deleting process should only take 5 minutes tops.

3. Go into Device Manager and delete the Boca Video Phone Classic BVPSZ1

4. Shut down and restart the machine. Once the system restarts Windows 95 will find the multimedia device again. At this point put the floppy disk in your drive and if the end user has Windows 95 versions 4.00.950 or 4.00.950a make sure that you choose "Disk Provided by Hardware Manufacturer" and click OK. For end users that have Windows 95 ver 4.00.950 B let the Update Device Driver Wizard locate the driver file, but make sure that it is in fact pointing to the A:\ drive. TIP: If OSR2 is pointing to the A:\ Drive the line where it reads "Location Of Driver" will be EMPTY. If there is a path there then click on Other locations and then type A:\ in the field provided.

5. In either case click on Finish. Once the files are copied to the hard drive the system will ask you if you want to restart. Click on NO.

6. At this point we copy the NEW VDMAMEMD.VXD to the Windows\System directory. Once it is copied go into Windows Explorer and look in the Windows\System directory, find the Vdmamemd.vxd and right click on it > Select Properties. The file should be 6KB (6,144 bytes) and should have a file version of 1.004

7. After you have verified that the file is the correct size and version, you may restart the machine.