naaloh

Member
  • Content count

    25
  • Joined

  • Last visited

Community Reputation

0 Neutral

About naaloh

Profile Information

  • OS
    ME
  • Country
  1. Something shall happen if you just find enough patience to wait... or at least to read this thread.
  2. The bottom line is if you just wait long enough you'll get your list of updates and when you install them the trouble will be gone, so there's zero need to install anything unofficial. Patience is a virtue.
  3. Well, I tried it and, not surprisingly, it didn't work. There is an exclamation mark on top of the adapter sign in the device manager and a massage that says "This device is either not present, not working properly, or does not have all the drivers installed. (Code 10.) Try upgrading the device drivers for this device." The .inf is, probably, OK, but the modem needs newer versions of drivers, which are available only for Windows XP and above.
  4. I'd say... If your primary concern is being able run relatively recent applications, use Win2000. If you have some applications that require real-mode DOS (most DOS apps do not require it and can be safely run from Windows) and you need to run them often, use Win98. In other cases use WinME, you can still run DOS apps that require real-mode, but you'll have to reboot your machine before and after that, which is much less than convenient. In all other aspects working under WinME will most likely be far more rewarding than under Win98, unless you want to run it on a machine with 32 MB of memory.
  5. I can answer that question now, as I found that I did save this information, it's USB\Vid_12d1&Pid_14db\5&1f8fd7d0&0&1 I have rewritten the INF file to the best of my abilities in order to make it work under WinME (and Win98, too). I am attaching the rewritten INF to this message, if anyone with a substantial knowledge of Microsoft INF files can check it for mistakes, I would appreciate it, because soon I'm going to borrow the modem again and try to make it work under Windows Millenium Edition. It's very frustrating that so few modern USB devices have drivers for the legacy OSes even when it doesn't cost anything for the manufacturer to provide them (all that's needed in case of this modem is a properly written INF, since the drivers themselves are from Microsoft). I imagine having a working WinME driver for such modems would help a lot of people, e. g. those who would like to use an old notebook that can't handle XP as a netbook. In case anyone is interested, I used Microsoft INF template for USB Remote NDIS Device for Win98/ME, Microsoft INF template for USB Remote NDIS Device for Win2000/XP, ZyXEL USB ADSL Modem INF for Win98/ME and ZyXEL USB ADSL Modem INF for Win2000/XP as a reference. The Microsoft templates are in the packages submix8c much helpfully pointed me to: RNDIS-USB-Kit_05.exe and rndisusb1-1.exe. WceIS.inf
  6. It's nice to see so many replies with so much information, I do appreciate this Upon examining the contents of the "HKEY_LOCAL_MACHINE/Enum/PCI" key I came to the same conclusion as CharlotteTheHarlot, i. e. that the number of the slot can be determined by the hex digit subkey. In my case there are the following subkeys. 000800 - Video Card , both the one present at the time of the backup and the one installed before that, they were actually in the AGP slot, not PCI 30F000 - DVB Card 38F000 - Sound Card 48F000 - Network Card, it was removed before backup 48F000, 49F000, 4AF000 - USB2.0 Controller, to the best of my recollection, it was indeed installed in place of the removed network card 50F000 - Modem 58F000 - IEEE 1394 Controller This could be translated into AGP - Video Card PCI1 - DVB Card PCI2 - Sound Card PCI3 - USB2.0 Controller, previously Network Card PCI4 - Modem PCI5 - IEEE 1394 Controller Which is plausible, because as far as I remember, IEEE 1394 Controller was, indeed at the bottom, however, it's strange that there is no 40F000 subkey and the USB2.0 Controller has three different subkeys. The latter is probably due to the controller being a composite device, but I see no explanation for the former. I do have access to it, but it's running under WinXP now. To ensure I was right in my interpretation, I could place devices in the order I deduced, install WinME and see it the results are the same.
  7. I have a registry backup from a WinME machine. I want to know which PCI device was in which slot at the time of the backup being made. Would anyone be so kind as to tell me which keys I should examine to determine this? Thanks in advance.
  8. submix8c, are you referring to the modem as "SIM card"? I suppose so, since I don't believe you would seriously think it's possible to burn the CD image to a SIM card. The virtual CD image is stored in the modem firmware, so it's contents can be changed when re-flashing the firmware. But that's not really important, the real problem is making the virtual network adapter work on OSes below XP SP3 (WinME in my case). The modem I experimented with is a Huawei E303. It is probably SIM-locked, thought I didn't try using it with any SIM-card other than the one it came with. Can't tell, since I currently don't have the modem and didn't save the state of the virtual machine I installed it onto. But why would it matter? Anyway, thanks for all the links. I think it's worth trying to make it work with the driver from Remote NDIS USB Driver Kit, although it's possible it will only work with newer versions that are only available for 2000 and XP. HiLink modems are controlled via web interface (browser), like DSL modems, for example. The only "client app" is the one that autoruns from the virtual CD to switch the modem state.
  9. Several cellular operators sell those Huawei HiLink modems (for example Huawei E303) advertising them as "requiring no drivers". This is, of course, not true for very obvious reasons. What really happens when such a modem is plugged into a Windows PC is its identification as a USB CD-ROM drive with a CD in it. After that this "CD" autoruns, the autorun program switches the modem state, the modem identifies itself as a virtual network adapter, for which the driver is then installed. The virtual network adapter shows as Windows Mobile-based Internet Sharing Device in the Device Manager. The driver it uses comes from the virtual CD mentioned earlier. It's in the MobileBrServ\data.bin ZIP archive, in the driver folder. Two files: wceis.cat and WceIS.inf. It seems to be made by Microsoft for one of their Windows Mobile based devices. The modem installs and works on Windows XP SP3, but not on SP2. However, since it uses standart Microsoft drivers, I wonder if it can be made to work on OSes below XP SP3, particularly Windows ME. Maybe if we identified the device, for which the Microsoft-written driver that this modem uses was intended, we could find out more about it. The driver file is attached to the post. The virtual CD image is uploaded to [url=]http://d01.megashares.com/dl/6uuqPbd/HiLink.ISO. Anyone is welcome to share his thoughts on the subject. WceIS.inf
  10. So the drives themselves always have PATA interface, while LPT1, USB, PCMCIA, etc. are the possible interfaces of their enclosures. Was it not possible to produce LS120/240 drives with FDD interface, so that they could be installed in place of a regular floppy drive? Surely, the read/write speed of LS120/240 drives would not exceed the bandwidth of the FDD interface, so it must be some other limitation, any idea what it was?
  11. I noticed that this page of the MDGx website ends with the following passage: This is not exactly correct. On Windows ME I was able to add DWORD values in accordance with this MSDN article, namely by using the 0x00010001 flag. I don't know if it works on Windows 95/98, but Windows ME entries like HKLM,Software\Microsoft\Windows\CurrentVersion\SharedDLLs,%11%\atl70.dll,65537,01,00,00,00 do produce the desired DWORD values in the registry (0x00000001 in the sample entry). The MSDN artice is also useful because it lists all possible flags. For instance, you can use 65539 instead of 65537 to keep any existing value in the registry instead of replacing it.
  12. Hi, Multibooter. Thank you for the thread it was very interesting, if only for academic purposes I want to ask the following question: which types of interface can an LS120/LS240 drive have? I've seen "parallel" and "ATAPI/IDE" mentioned in this thread. Am I correct to assume that the first means LPT parallel port, commonly used to connect graphical printers, and the second means Parallel ATA interface, commonly used for HDDs, CD and DVD drives? Are those two the only types available natively (not counting USB bridges)?
  13. What abot the updated runtimes of Visual C++ 2003 SP1 from Visual Studio 2003 SP1 MFC Security Update? Were they intentionally not included in your service pack or are there some problems with those updated files?
  14. Can you tell me how thoroughly your service pack is tested? I mean, should ATL80.DLL v. 8.0.50727.6195 cause any problems on Windows 98, how likely is it to be reported? Although I don't use Windows 98, I could use your service pack as a reference regarding the most recent versions of dlls to work on Windows ME, unless it includes KernelEx, which I'm not planning to use.
  15. So there's an even newer version 8.0.50727.6195 of Visual C++ 2005 runtimes: Visual C++ 2005 SP1 MFC Security Update. But why didn't they include ATL80.DLL from this update into their "98 SE SP 3.4"? The post you point to lists ATL80.DLL as 8.0.50727.4053 while everything else is 8.0.50727.6195. Did they found some problems with ATL80.DLL v. 8.0.50727.6195? I don't know. Just wanted to have the most recent working runtimes just in case.