Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


cov3rt

Member
  • Content Count

    399
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    1

cov3rt last won the day on June 28

cov3rt had the most liked content!

Community Reputation

13 Good

About cov3rt

Profile Information

  • OS
    none specified
  • Country

Flags

  • Country Flag

Recent Profile Visitors

3,344 profile views
  1. do you know which exact intel chipset inf update you used? for video driver, you'll likely need either the extended kernel or unofficial update rollup v11 installed from beforehand, however, due to certain pre-reqs, and what have you, it's unclear what to install and when. i do not use the "extended core", but i do use the unofficial update rollup v11 that allows installing / using newer applications, such as kmeleon 76. it's a bit confusing, because there are these newer intel chipset inf updates up to haswell, yet you have this usb problem on these newer systems, what am i missing here? according to your experience, it seems that the newest or at least "newer" intel inf update packages wouldn't cause usb related issues if you had deleted the usbhub20.sys in your case at least. but in terms of solutions and what to do is all of over the place, as the method i linked has not been confirmed or has it?. 9.4.2.1019 PV is the newest intel inf update package i was able to find with mention of windows 2000 support in the readme. honestly, i would rather go with the modified usb file way slipstreamed, with the assumption that inf updates wouldn't mess anything up. btw, you can get the unofficial update rollup v11 from here "http://sdfox7.com/2000/Important_EOL_Updates/Windows2000-UURollup-v11-d20141130-x86-ENU.7z" as for haswell 4th generation intel graphics ( specifically for intel hd 4600 ), you might be limited to uni vga display driver, as i think intel hd 4000 is the last unofficial versions to work.
  2. does your 2K SP4 install cd have the custom "USB.IN_" file? i have no way of knowing if this fixes the usb related issues, however, maybe you can modify your installation cd with nlite to include the modified usb file below. i uploaded in the other thread below, mentioned in the 5th post. https://msfn.org/board/topic/181573-win2k-fully-patched-iso/
  3. the storage device currently has windows 7 installed with the entire drive partitioned as one, so it does not seem that i can tinker with it, at least, from using disk management, i was not able to create another specific volume, and how would i go about making a fat 2000 MB partition? maybe windows 7 recovery disc command prompt portion with diskpart if i'm choosing to wipe the drive to install windows 2000 from scratch, can perhaps format a individual partition in either fat or fat32? at least, i tried to format the drive in fat32 as a method before giving up to install windows 7, it said it couldn't, because the storage size was too much? but i find that odd, because isn't fat32 able to use up to 2 TB? at least, that's what google just said right now of searching. anyways, i found an idea that might work, which would require me to wipe the storage device ( would need to do so anyways to install windows 2000 ), and in windows 7 setup, delete the drive completely, reboot into the setup again, create a new partition, then use diskpart to format that specific partition into fat32 of no more than 32 GB, then when installing 2K, assuming it is able to detect the drive now, then delete the 32 GB partition and partition the entire drive ( 223 GB ) ?
  4. yeh but what type of w2k install cd did you use? was it a custom one, SP4 version, etc? also, you didn't mention any other bios settings, and by legacy mode, i'm assuming you mean it was a bios setting for allowing the drive to be detected as an ide device? the only thing i can think of is for some reason that i'm not noticing / seeing, the usb installation is not compatible with newer / certain chipsets, at least, i only tested the usb way one time before and it worked, however, i don't remember what exact chipset i tested on or the exact setup, but i do know it wasn't newer than any of the core 2 duo based systems. the bigger issue is not being able to find some kind of bootable usb partition manager ( all of them were paid ) so that perhaps i could format the drive as MBR based device, at least, from what i read somewhere, it might have been a reason for why the device is not being detected? but would that mean that blank drives ( drives you obtain in brand new conditions at least ) are MBR formatted from the beginning? but i think i read somewhere too that the windows built in format tool would automatically format to MBR, but i don't know if this is true or not. also, if i didn't mention, i also tried the "compatibility" mode in bios from before, instead of "AHCI", but it didn't make any difference, as soon as the bootable usb fired up into it's application, it immediately mentioned of not detecting any storage device, and even selecting the manual detection options had made no difference. usb itself was working in the setup portion, as i was able to hit fn+f5, f6, f7, etc, and i also tried the standard pc option, but it made no difference, either it would hang on setup is starting windows 2000 part, or it would give the stop error of inaccessible boot device.
  5. i am having trouble figuring out how to install windows 2000 sp4 via usb installation under a haswell qm87 chipset. i used a software to prepare the usb storage device with windows 2000 sp4 burned onto it. i have used the program before and was able to install windows 2000 sp4 via usb, however, for this system, it does not seem to work, but i don't know if it's because i didn't follow the instructions properly and / or the laptop simply doesn't like windows 2000. the usb device was formatted as NTFS default allocation size of 4096 MB before i used the software to burn it onto the usb. for bios settings, i tried various different ways, uefi enabled / disabled with cms support, with or without usb 3.0 enabled, etc. i also removed the storage device to see if i can figure out a more specific issue, apparently the usb doesn't even get detected when the actual windows 2000 setup portion begins, because when i try to press f5, f6, f2, f8, f10, etc, nothing happens, also it of course just hangs on the setup is loading windows 2000 part. there is also a compatibility mode for the sata controllers, ahci or compatibility, but that wouldn't matter if the usb isn't being detected in the first place. what i did notice is that the usb software says no driver found, no matching pci ids in driverpack.ini. i was wondering if anyone has any suggestions, maybe perhaps a different way of burning onto a usb / formatting options, etc, and / or maybe additional slipstreaming? maybe i need to slipstream a specific usb 3.0 package?
  6. just as a heads up, based off the readme / release notes, odyssey client 2.20 oem was the first version to support wpa, so even if odyssey client 2.0 worked / installs on windows 95, it would be limited to wep.
  7. thanks for the info, i was able to confirm the issue, it wasn't the drivers to begin with as 6.1.3.0 did work properly, i simply didn't have the ethernet cable plugged all the way on the modem end, so it was just a loose cable problem, which can happen if your network cable doesn't have the lock clip design and / or is missing from damage.
  8. for odyssey client 1.10, there's not much incentive to try it / use it, since it doesn't even support wpa? however for odyssey client 2.20, it does mention support for wpa for certain wifi adapters. i do actually have windows 98 installed on the laptop now, and i may install the 2.20 client temporarily so i can copy the installed program and use it for possible experimenting in the future for windows 95.
  9. wpa2 would be overkill, but odyssey client 2.2 did mention wpa. if we could have someone somehow create a custom odyssey client 2.20 package so that it can work with windows 95, we may be able to get it work the way that wsc guard 4.0 does. the dell truemobile 1150 could possibly work with it IF adding "%Wlluc01.DeviceDesc%=Wlluc01.Install, PCMCIA\Lucent_Technologies-WaveLAN/IEEE-C4F2" for cardbus or "%Wlluc02.DeviceDesc%=Wlluc02.Install, PCMCIA\Lucent_Technologies-WaveLAN/IEEE-C043" mini pci card versions to the same package as the newest orinoco driver which might have supported WPA, being that C4F2 is identified as C908 and C043 is identified as 911F in newer Operating systems such as 98SE. it also explains why somehow oddly, i was able to flash the dell truemobile 1150 with the unofficial 8.72 firmware under windows 95 when i used the 7.64 driver with added C4F2 hardware id. and like i mentioned previously in my other post, a while back, there might have been a driver that supported wpa, from package "AirLancer_11Mbit_Win_95_SR02-2.1.zip", however, i was never able to re-locate this, however, after reading the readme section of the latest drivers from orinoco for 98SE at least, SR02-2.3 appears to be the first version with wpa, not SR02-2.1 mentioned in the other package. maybe someone can acquire one or other packages and create a modified driver along with the modified odyssey client 2.20 or wsc guard version? i tested both 4.0 and 2.40 of wsc guard, they install but have a missing export, i think it was called something like getfolderpath, but the odyssey ones of course simply wouldn't install due to restricted installers, where removing the "LaunchCondition" using orca made no difference, even when trying to do so from using the extracted msi from the temp folder when in the process of installing from the regular .exe file.
  10. i was wondering if the bios has the option of plug and play o/s yes / no, if selected No, would this be the same thing as installing windows 95 or 98 with "setup /p i"? so that if the bios does not have the plug and play o/s option, then "setup /p i" should only be done if normal "Setup" does not successfully finish installation and / or buggy operation is found? how i see is that for 98SE in particular, i would WANT to have ACPI working and installed, and therefore if the bios has the plug and play o/s option, i would set to yes first, install with normal "Setup" and configure onwards, however, if installing with yes is problematic, then start from scratch with the no option with normal setup, and if the bios doesn't have the plug and play o/s option, then just setup, and if normal setup doesn't work, lastly to use "Setup /p i" or other customized switch. for windows 95, due to not having any support for ACPI, it seems like the setup /p i option should only be used if normal setup doesn't work properly and / or bios doesn't have that pnp O/S option. but would you also have to do setup /p i, even if pnp O/S is set to NO? i got the pnp bios info in the link below. http://help.cognex.com/Content/KB_Topics/VisionPro/Drivers/2905.htm
  11. when i try to install "user-agent-switcher-0.6.10-bump.xpi", it asks whether or not i should install for the profile or just the application folder? does it matter which one i select? i selected no. i also noticed that youtube.com still doesn't work properly with the "user-agent-switcher-0.6.10-bump.xpi" installed. it still shows greyed out text merged onto the left and no search box.
  12. i was wondering which driver version / package can you guys confirm working for the intel pro 100 ve network connection ( mobile adapter ) on windows 95. is it for the hardware id "PCI\VEN_8086&DEV_2449". i do not have the entire subsys portion at the moment but i can possibly get it later. i tried the 6.1.3.0 driver, but i was not able to get it working at the time. complaining on dhcp related errors in winipcfg when i tried to release / renew ip addresses. in device manager, it was listed as "working". i think i tried the 5.x family of drivers, i think it was the one ending in .34, but i also couldn't get it to work with that either, but i suspect it's possible my windows installation was somehow missing components / corrupt, as i was working with a very poor condition hard drive that's basically gonna fail soon, it has about 109,000 hours of operation on it. there is this 1.0.0.1 driver that is ndis4 based, which i suspect could work, although it carries different files in the package, and i don't see the wol558.vxd for example, that is included in the other packages. now according to one site, windows 95 osr2 can use ndis4, and i checked my files and some of the ethernet adapters do indeed have ndis4 system files in their inf packages, such as the realtek 8139. according to another source, i think it mentioned that windows 95 osr2 or newer requires ndis4 or that windows 95 version A only required them, but i don't know for sure. i posted the links for the sources below. i would rather use a older driver for ethernet so i can just use that for all systems i test on, but at the same time, i would want to have a better idea of why i couldn't get these drivers to work. all i need is a inf package, no setup or utilities needed. would be nice if someone can upload the inf package for me to test.
  13. thanks, i had located it earlier. installation can be done by going into specifically the "D:\plus" folder and running setup. you can unselect system agent as i believe it's unnecessary, also it may complain of drivespace 3 already installed, just bypass it by pressing ok or w.e, and all else should be fine. you can also unselect "show window contents while dragging" for better performance and unselect "show icons using all possible colors", also you can now check "stretch desktop wallpaper to fit the screen" in the plus tab that's found by accessing properties from right clicking desktop. the wallpaper stretch option is not in the same drop menu of the display adapter resolution window in which i thought it would be, no biggy, but just know that it's controlled through the plus tab.
  14. the link you referenced to didn't relate to my problems, however, i was able to achieve new results with some methods i applied. oddly, the firmware update wouldn't work / detect the card with the original driver dated in late 2000, however, upon some weird tinkering, i was able to somehow get the unofficial 8.72 firmware updater to work ( pc card version ), i also have the mini pci version fimrware update as well. what i did was unchecked the read only option for the inf of WLLUC41 from package of "NDIS 3 Miniport Driver for MS-Windows 95 Variant 1 Version: 7.64", and then added "%Wlluc01.DeviceDesc%=Wlluc01.Install, PCMCIA\Lucent_Technologies-WaveLAN/IEEE-C4F2" to the inf, saved, re-installed the driver from device manager using have disk method, selected the "ORiNOCO PC Card (5 volt)" option, copied files from appropriate areas. the wizard may not work properly and ask for a file that already should be copied, simply point it to the folder with the browse option and it should work. after this, i was able to update to the unofficial 8.72 firmware. however, for the client manager, none of them seemed to work, regardless of whether i tried the dell 1150 specific ones or the orinoco client manager. although i didn't write down specifically which ones i tested, i believe the 3.30 dell / orinoco clients did not work, neither did the 2.58 / 1.71 ones, and i don't think i went lower because i didn't see a point in using version 1.58 or older. now what did "work" was going back to the actual dell truemobile 1150 ndis 3 driver dated in late 2000, and using dell truemobile 1150 client manager ( pc card version specifically ) version 2.58, with 1.58 version also working. i did not have a way of actually testing the wifi card itself and it's application and connecting to a access point, as it's limited to wep or open wifi, none of which am i able to do, though the application / way of connecting seems a little farfetched, because it has like two seperate applications, but anyways, that's for a different discussion. now the thing is, i do not believe i tested the 2.58 and 1.58 dell clients before the firmware upgrade, so it's possible that it still would have worked, but there's another issue with the fact that it's unclear on the exact functionality of the driver, as well as the 8.72 firmware, as it's shown in clients 2.58 and 1.58, and as a reminder, these were the dell clients. indeed the card is identified as a form of gold card in the dell 2.58 and 1.58 clients, so it does appear to be some kind of rebranded orinoco gold card. you may be able to also add "PCMCIA\Lucent_Technologies-WaveLAN/IEEE-C043" to the 7.64 inf as well ( for unofficial firmware 8.72 to work, and then go back to the older actual dell 1150 driver so you can configure it will the dell truemobile 1150 2.58 or 1.58 specific client manager ), however, i did not test the mini pci version yet and i did this after all of the steps mentioned here. other than all this, the laptop's intel pro 100 ve network connection with dev 2449 does not work either, and i'm not sure why, i noticed that winipcfg can't release or renew ip addresses for it, and complains of a dhcp related error, something to which i never had, unless it was a card such as the dell truemobile 1150, limited to wep, etc. i used the 6.1.3.0, as well as the older 5 series driver in 2001, but doesn't seem to make a difference.
  15. can you please specify which driver version to use for dwmapi.dll, as well as for dcflibrary.dll & odlib_ossl.dll. also, i could not find a way to install the client on windows 7, installing with the original package made no difference. is it possible for you to just upload the already installed program that you used on windows me to that easyupload site, that way i should be able to copy the program to the windows 95 system and test with those 3 dll files i downloaded already. this is the only option i can think of, unless something unless practically can be done. i probably will not wait anymore than a day as i need to move on from this experimenting.
×
×
  • Create New...