draco

Platinum Sponsor
  • Content count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About draco

  • Birthday

Profile Information

  • OS
    98SE
  • Country
  1. Too late. And the configuration program from Ralink is flaky -- I have to continually select the field to enter each character of the SSID and the Passcode (WPA2). What a pain. What's this about the .inf file? Where can I find information about the structure of this file. I've tried to install drivers in the past on both XP and 98SE with little luck. I always had to resort to the installer code. The system didn't seem to recognize the actual driver. On 98SE, I had to modify a .inf file to get it to recognize my video adapter. This for a laptop. I was successful, but the adapter wasn't listed in the .inf file, so I had to add it. The driver ought to be somewhere among the drivers I have for the Dell Latitude C810, but I don't know where to find it. Mayhap it resides in a CAB file somewhere... Thanks for the reply and the thoughts. The rebranding makes sense. I may also check out the serial number of the adapter since that encodes the version number, in case I'm missing something. Regards to all, especially puntoMX. draco
  2. Long ago and far away, I purchased three Linksys WMP54G wireless adapters for my XP systems. They worked well. One day an evil elf delivered unto each of my systems an upgrade which disagreed, occasionally with my adapters, generating c++ errors and disconnecting my adapters and requiring a reboot of the system. I tried to find an updated driver from Linksys, but they had only the originals. After searching the web, I uncovered information suggesting updated wireless adapter drivers from Ralink (rt2500.sys) which actually solved the problem in the first PC. I later made the same change to the other two since the c++ errors were quite annoying. This weekend, as I contemplated placing the same wireless adapter in a fourth PC, I found that Linksys has some new drivers available. Not being sure whether I had v4 or v4.1, which are different drivers, I pulled the adapter from one of the systems only to find that it is v1 which uses a different chipset -- one from Broadcom. How can this be? Should the Ralink driver even have worked? Any thoughts or comments? At the moment, I'm slightly confused and full of awe and wonder. I thank you for allowing me to capture your mind for the time it takes to read this. Kindest Regards, draco
  3. Thanks for the info. I had never heard about 5 1/4" double-sided 720k drives before. Were they common? Here's the latest on this project: the modified vcache worked perfectly. Anadisk works in the 98SE environment, although it shows spurious sectors on the floppy diskettes; When Anadisk is asked to report on those sectors, they disappear. I regret that I did not confirm which version of driver.sys that I was using. I will need to check that later. As for now, everything is working well enough. We can reboot to 98SE when we need to analyze diskettes and we can read them using 98SE. We can copy them to the Fixed disk and prepare them for writing to CD-Rs. We can then reboot in XP and use our CD writing software. What an interesting adventure! Thanks to all for your ideas, assistance and encouragement. Kind Regards, draco
  4. Do you get the message: "There is not enough memory available to run this program."? That's an easy one! Just install the FREE - Xeno86's modified VCACHE.VXD (direct download) BTW, which driver.sys did you try? Yes, that is exactly the message we get when we try to open the DOS prompt. I had seen that some entry/entries in the system.ini file would cure that message, but I've been unable to keep in my mind exactly what the entry/entries were. I work on this box about once per week, usually on Friday, trying to pound it into shape. Last week, we installed a wireless PCI card so my sister could access the internet through her home network. After getting both partitions to recognize the network and getting IE6 and Firefox, I tried to wake up the floppy drive. I expect to tackle this DOS memory issue later this week, Googling to find the required statements. You have simplified my task immensely. Much gratitude sir. As for which Driver.sys, I cannot swear to it and having since loaded 98SE onto the partition, I may have overwritten what was there. I expect it was from the 98SE release. I'll see if I have the source for the MS DOS 7.1 that I loaded on the drive and the PC DOS 7 to see if Driver.sys resides on any of those. Do you think it's possible that I used a non-working version? Regards to all
  5. Thank you for your reply and your picture. You helped me confirm that we were on the right track. Here's what we did: We swapped the floppy drive and cable from a working XP & PC DOS 7 system (MSI-7005) which recognized the 5 1/4 drive (both were TEAC FD55-GFR, same jumpers) with out any change. The drive and cable from this system (MSI-6728) worked in the other system (MSI-7005). So it wasn't a floppy or cable problem. The BIOS indeed shows 5 1/4 1.2M drive as B: just like your picture. We tried Driver.sys and Drivparm, with the same results but different drive letters. We solved our problem by installing 98SE on the partition. Good old 98SE recognizes both drives (like XP does) AND allows us to read the diskette at a low level using ANADISK. I'm still confused about why PC DOS 7 and MS DOS 7.1 (98SE) refused to recognize the diskette drive; I thought it must be that the driver was missing from the OS which is why we tried Driver.sys and Drivparm (under MS DOS 7.1). PC DOS 7 never would boot from the hard disk, but MS DOS 7.1 booted up just fine, although we still had the diskette drive issue. The two systems differ in the model of their motherboards and in BIOS makers -- the one which always worked (MSI-7005) was Award, and the one which gave us fits (MSI-6728) was AMI BIOS. Perhaps something lurks in the BIOS which requires a Windows OS to work properly... We still have some work to do -- We cannot run programs from the DOS prompt because the box has 1 GB. But persistence paid off. Thanks to all, especially Dencorso.
  6. We finally got to test: we replaced the diskette drive (a Chinon with a TEAC) and we replaced PC DOS 7 with the DOS from Windows 98SE. The good news is that the DOS from Windows 98SE boots up. It seems the Mobo (an MSI 865PE Neo2 Version 1.1 MS-6728) doesn't like PC DOS 7. Windows 98SE DOS has a separate partition and uses FAT 16. That way we can copy data to the SE partition and read it from the XP partition. Except --- Although Windows XP Pro still recognizes the floppy drive, the DOS from Windows 98SE does not either.
  7. Thanks for the pointer. We will check this out on Friday when my sister and I get together. It's her computer and she's using it to read and capture the data on all of those 5.25 disks that she's collected over the years. I see that you are a 9x/Me guru. I may need some help with that, too. But later.
  8. Here's a good one: We have an XP PRO system (MSI mobo, P4) with two recognized floppy disk drives, A: 3.5, B: 5.25. When we boot to PC DOS 7.0 on the A: drive, it doesn't recognize the B: drive, but Anadisk, which we run from a ramdisk (C:) reads all the sectors, finds all of the formatting information, and lets us look at each sector, each file whether deleted or not, and the FAT. Why doesn't DOS recognize the B drive? Could it be the DS0, DS1, DS2, DS3 selector? Would XP recognize the drive if the DS selector was incorrect? Would Ananisk? Any ideas? We are using Anadisk because some of the diskettes are copy protected and some are CP/M and maybe Pascal P code. Anadisk also allows us to format the diskettes to erase all of the old data. And Anadisk doesn't run under XP. Because we can read DOS flavored diskettes on XP, and because Anadisk can read the diskettes and because the drive worked on the machine from which we pulled it, we think the drive and cables are good. And the POST tickles both drives on boot up, too. TIA.