Jump to content

DougB

Member
  • Posts

    134
  • Joined

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by DougB

  1. This is a relevant listing of the installation zip for one modem (Actiontec EX560LKU -- this is a combo serial/USB modem): 2,175,846 setup.exe <dir> INF/ <dir> INF/INF_USB_PL/ <dir> INF/INF_USB_PL/Win98ME/ 22,396 INF/INF_USB_PL/Win98ME/prSeEnum.sys 9,841 INF/INF_USB_PL/Win98ME/PSERENUM.VXD 33,300 INF/INF_USB_PL/Win98ME/SER9PL.SYS 2,281 INF/INF_USB_PL/Win98ME/SERSPL.INF 26,711 INF/INF_USB_PL/Win98ME/SERSPL.VXD 8,832 INF/INF_USB_PL/Win98ME/SERWPL.INF <dir> INF/INF_EX560LKA_V31/ <dir> INF/INF_EX560LKA_V31/Win98/ 7,910 INF/INF_EX560LKA_V31/Win98/MDMATEX.CAT 57,586 INF/INF_EX560LKA_V31/Win98/MDMATEX.INF And this is the listing of the installation zip for the other modem (Dynex DX-M300 -- USB only): <dir> Win98SE/ 168,152 Win98SE/242004usa8.exe 65,536 Win98SE/CARPDLL.DLL 4,608 Win98SE/carpserv.exe 248,858 Win98SE/CNXStd.cty 316,928 Win98SE/csacpl.cpl 27 Win98SE/CUSBUT2.cat 3,265 Win98SE/CUSBUT2.inf 27 Win98SE/CUSBUTm.cat 25,574 Win98SE/CUSBUTm.inf 23 Win98SE/disk1 6,633 Win98SE/firmware.bin 153,984 Win98SE/HSFHWCD2.sys 585,856 Win98SE/HSF_CNXT.sys 1,067,008 Win98SE/HSF_DP.sys 479,232 Win98SE/Hxfsetup.exe 69,632 Win98SE/MdmXSdk.dll 11,011 Win98SE/MDMXSDK.sys 1,400,842 Win98SE/modem.cab 27 Win98SE/OUSBUT2.cat 3,277 Win98SE/OUSBUT2.inf 27 Win98SE/OUSBUTm.cat 27,705 Win98SE/OUSBUTm.inf 22,400 Win98SE/STRMDISP.SYS If it would be of any help, i can PM you the INF files. - Doug B.
  2. This system would be just fine. Thank you Ok, i'll do a clean install on my USB 1.1 system and test the USB tele modems tonight. So the results are useful, tell me if there's anything awry or dis-recommended with the following steps (this is my normal procedure): 1) Wipe hard drive. 2) Install Win98SE. 3) Install Intel Chipset driver. 4) Install video driver. 5) Install IE6 SP1. 6) Install uSP 3.0 2012-Apr-23. 7) Install USB modems, one at a time. Q1: Skip any step(s)? Reorder any? The installation instructions for the modems state to run their setup program first, then reboot, then plug in the modem. Q2: Do it that way... or do it by plugging in the modems without the manufacturer-supplied drivers installed? Q3: What result/bug reports will be useful? Installation success/failure? Operational success/failure? BSODs? - Doug B.
  3. Ok, i have a couple of USB tele modems (not currently installed) and would be willing to test, but here's the rub: 1) The system i've been using to test uSP 3.0 final is kind of ancient (PII/i440) and only has USB 1.1. 2) My main system is somewhat newer (P4/i845) and has USB 2.0, but i'd have to first install uSP 3.0 final over currently-installed uSP 3.0b4. I'd be a bit nervous about doing that over the next couple of weeks, because it's my primary link to work and the 'net... and i have some work projects that'll be due. For the same reasons, i can't do a new, clean install right now. But i do want to help the project along, so maybe i'll just bite the bullet and give it a go anyway. Let me ponder.... Any feedback is appreciated.... - Doug B.
  4. Regarding the current backup issue, i appreciate your work on documenting/pre-troubleshooting uSP installation on your web page. However, i have misgivings about one line: "Restoring windows 98 can be done simply be recopying all the system files back to their original location, in dos mode." The DOS internal COPY command should *not* be used for this! Some of the Windows system files or folders (perhaps installed by non-Ms programs) might have long names. Copying with the DOS COPY command will rename the copies to short names. This could make the restored system (at least partly) non-functional. I have successfully backed up Windows many times in pure DOS (*not* in a DOS window) using either of two free methods... neither of which is what i would call "simple": 1) Using Odi's DOS Tools For Long Filenames, which contains the LCOPY.EXE and LDEL.EXE programs. (You don't need a LFN driver with this method, and the case of switches is not important.) To store, go to the target directory and do: lcopy /a /s c:\windows\* "/A" includes files with system and/or hidden attributes also, "/S" recurses through subdirectories, and "*" makes sure every file from the source is copied, whether they have an extension or not. Make sure the target directory is empty before you do the copy. To restore, go to C:\Windows\ and use: ldel /a /s /f c:* "/F" deletes folders too. Then do: lcopy /a /s d:\path\* where "d:\path\" is the drive and path to your backup. 2) Alternatively, first run a memory-resident LFN driver (Jason Hood's DOSLFN is an up-to-date driver), and then use a LFN-aware archiver/unarchiver. I've found that PKZip crashes with large numbers of files/directories, so the Info-Zip 32-bit archiver is my choice. To store, start by installing the LFN driver. Then go to the target directory and do (the case of switches *is* important): zip32 /r /S -9 zipfile c:\windows\* "/r" recurses through subdirectories, "/S" includes files with system and/or hidden attributes, "-9" gives maximum compression (but is slower), "zipfile" is substituted with the name you want to give the created zip file, and "*" makes sure all files from the source are included, whether they have an extension or not. Make sure to choose a non-existant "zipfile" name. To restore, first make sure a LFN driver is installed. Then go to C:\Windows and delete all folders and files however you want to (LDEL.EXE as mentioned above is good, but there are other methods -- just make sure all files in and under C:\Windows\ are gone). Then do: unzip32 d:\path\zipfile where "zipfile" is substituted with the name of the archive file you want to restore, and "d:\path\: is where you stored it. These are the simpl*est*, free methods i can think of. The advantage of method 1 is that it is simpl*er* and quicker, but the backup is uncompressed and takes up more disk space. Method 2 is more complex and slower, but the backup files require less room. And yes... perhaps these posts could be moved to a different thread? - Doug B.
  5. Oops -- addendum to the previous. I ran 98SE2ME.exe from the E: drive, so maybe that's why those folders/files were created/copied there. Either way, they still should have gone to the C:\Program Files folder but didn't. - Doug B.
  6. I might have something useful to add to the "C:\Program Files" issue. I also get the "C:\Program cannot be found" message box after reboot... but more things also happen.... Some (all?) files from that destination never get copied there, but rather their folders get created on the drive on which the ME cab files are located (if the drive is writeable) in root directories. Case in point: For a recent install, i copied the cab files from the ME CD to a E:\WinMeCab folder (for quicker installation). After installation was complete, i noticed that the following folders were created: E:\Accessories E:\Common Files E:\Plus! E:\Pinball E:\Gamezone with the following files: Directory of E:\Accessories\ MSPCX32 .DLL 53248 06.08.2000 17:00 mspcx32.dll WORDPAD .EXE 204800 06.08.2000 17:00 wordpad.exe Directory of E:\Common Files\ <DIR> 04.10.2012 13:00 Microsoft Shared Directory of E:\Common Files\Microsoft Shared\ <DIR> 04.10.2012 13:00 MSInfo Directory of E:\Common Files\Microsoft Shared\MSInfo\ MSIAV .OCX 38912 06.08.2000 17:00 msiav.ocx MSICDROM.OCX 43520 06.08.2000 17:00 msicdrom.ocx MSIOLERG.OCX 35840 06.08.2000 17:00 msiolerg.ocx MSIPRINT.OCX 34304 06.08.2000 17:00 msiprint.ocx MSISYS .OCX 139264 06.08.2000 17:00 msisys.ocx MSUPDATE.OCX 30208 06.08.2000 17:00 msupdate.ocx TXTVIEW .OCX 28672 06.08.2000 17:00 txtview.ocx Directory of E:\Plus!\ The Pinball and Gamezone folders contained all their respective files -- i just didn't include them here to shorten this post. All these files *should* have been copied to folders in C:\Program Files, but wound up in newly-created folders on the drive containing the ME cabs. Could it be that somewhere in the installation files, there is a C:\Program Files or C:\Program Files\... that needs quotes? Anyway, i'm a big fan of 98SE2ME! I hope this report is of use. - Doug B.
  7. This hex-hack worked for me too, <snip> (Wondering -- would a W2K ntdll.dll work as well?) Ok, i anwered my own question -- the ntdll.dll from Windows 2000 Professional SP4 *does* work for SumatraPDF (same procedure as above), and it's file size is a bit smaller than the WXP SP3 version: 2K SP4: 491,792 bytes, v5.0.2195.6685 XP SP3: 706,048 bytes, v5.1.2600.5512 On the W2K Pro SP4 installation CD-ROM, ntdll.dll is located in the \I386 folder. Note that SumatraPDF web page states: "Supported OS: Windows 7, Vista, XP." - Doug B.
  8. This hex-hack worked for me too, except that i had to hex-edit the LibMuPDF.dll file as well -- there's one occurrence of "ntdll.dll" in the LibMuPDF.dll file and two occurrences in the SumatraPDF.exe file. I changed 'em all -- seems to be working fine (KEx v4.5.120). Remember to copy ntdll.dll from WXP to Sumatra's folder and rename it to "9xdll.dll". (Wondering -- would a W2K ntdll.dll work as well?) Thanks loblo! - Doug B.
  9. (Semi-)Clean Install Report Sorry for the long-ish post, but first off, i want to thank everyone, especially PROBLEMCHYLD, for all the work and input on this very-worthwhile project! Anyway, hope i'm not "jumping the gun" (as uSP 3.0 is not yet final), but just out of curiosity... and because PROBLEMCHYLD recently asked it... and because of potential issues reported in recent posts, i did a (semi-) clean install of the Apr-01 uSP release. I used an old IBM+Intel PII+440BX/ZX laptop that i keep around mostly to test Win9x non-KernelEx software compatibility. (I do use KEx on my newer main system though.) Here's how i proceeded: 1) Reformatted the harddisk. 2) Installed Win98SE (custom). 3) Installed Intel Chipset Software Installation Utility. 4) Installed video driver. (Couldn't stand to look at VGA 640x480x256 for too long!) 5) Installed IE6 SP1 (everything except OE and multilanguage). 6) Installed uSP "Main Updates" (without any of the options). 7) Installed all the uSP options except "IE Core Files" (both), "Performance Tweaks" (grayed out), and "Power Management Trouble Shooter" (grayed out). Everything seemed to go smoothly -- no noticeable installation issues, and the hardware and Windows boot up fine -- though obviously i haven't done much with it. And unfortunately, i don't have the means to test most of the options after installation. Note that this computer has USB 1.1 -- not USB 2.0. I don't know if that's significant in terms of testing uSP or the disk issues recently mentioned. Anyway, i installed no manufacturer-provided USB device drivers, and my USB flash discs, Zip drive, portable harddisk, diskette drives, camera (which appears as a flash disc), and a multi-card reader (which appears as multiple "Generic Storage Device"s) all installed ok after plugging them in. (The other card reader was not so lucky -- identified as "eUSB SmartMedia Adapter" -- Windows couldn't find a suitable driver. And i did have to tell the system that the portable harddisk was "removable" via Device Manager > Disk Drives > Settings; otherwise, it acted quirky.) Note that "Performance Tweaks" and "Power Management Trouble Shooter" options were grayed out -- "Performance Tweaks" probably because it has 96mb RAM (uSP 3.0 uses 128mb as the limit, whereas uSP 2.1a used 64mb), but i'm not sure why "Power Management Trouble Shooter" was grayed out. I noticed that Windows Management Instrumentation took a long time to complete after rebooting (Windows 98 Setup: "Updating System Settings...") -- i was starting to worry that it hung, but it finished ok. And a note of caution: Be extra aware that the "Windows 95 Shell Swap" option *significantly* alters the functionality of the interface... and a few of its changes are somewhat-annoying. I installed it rather absent-mindedly, and was surprised at the changes it wrought. BE CAREFUL NOT TO INSTALL THIS OPTION BY ACCIDENT! (Like by just clicking all the option boxes... like i did -- hah!) So overall, i'm quite impressed with the ease of installation, up-to-date-ness, and increase in functionality that uSP provides. (Except for the "Win95 Shell Swap" option as previously mentioned -- watch out!) It makes re-installing Windows 98SE *so* much-less painful and tedious... and much-less "hit and miss". Kudos! - Doug B.
×
×
  • Create New...