Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by cov3rt

  1. 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, as well as the older 5 series driver in 2001, but doesn't seem to make a difference.
  2. 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.
  3. i'm not sure if i understand. do you mean to say that if i were to install the client on any system, regardless of OS, then i need to have both the regular .exe file, as well as the msi version in the same package? but then which one would i need to install, the msi or exe one? just now, i tried to install 1.10 and 2.20 on windows 7 so i can then transfer it to the windows 95 machine to test, however, it had got stuck on the update drivers / registry portion, i had cancelled the wizard somewhat prematurely / ending tasks in task manager, and it still launched the client manager on windows 7. however, after i copied the programs on a usb to test on windows 95, when trying to launch on windows 95, it complained that some components are missing. hmm...., i may perhaps test one more time with both packages ( what it originally came as for both that i downloaded ), maybe it might yield better results? the reason why i excluded the msi was because i thought windows 95 might install "Better" or would only need the regular exe file and not the msi one? also for the dwmapi.dll file, is there a specific version i need / more compatible version for windows 95?
  4. i have tried to update the firmware of the dell truemobile 1150 cardbus wireless adapter on windows 95, as well as on windows 10 tested too, but both complain of no wireless card driver found. now, for windows 10, i haven't installed the driver yet, but for windows 95, i did have the driver installed. the full error code is "no wireless card driver found. make sure the right driver is installed, and the wireless card is inserted. please check our website for information about the latest available drivers and firmware updates." now the firmware utility itself also mentions no card information available, and this was for the official 6.16 dell firmware one and i also tried to test the 8.72 unofficial one, cardbus and mini pci both gave the same error. has anyone had any experience trying to update the firmwares on these cards? i don't remember, but a long time ago, i might have gotten at least the official 6.16 firmware to install, but i think it was a mini pci version so the scenario was a little different. on windows 95, the driver is installed and considered "working" by device manager, but even the agere / orinoco client manager 3.30 application i installed doesn't detect it, despite it supposedly mentioned as doing so elsewhere ( indirect source from a dell forum ). i wouldn't want to update the firmware elsewhere, because that wouldn't be a practical solution for people who would wan't to configure the card from windows 95, so what exactly could the issues be of it not detected the card / the firmware complaining that it's not compatible, as that was another error, specifically from the unofficial 8.72 firmware i think.
  5. i've been going back and forth with trying to install these clients, using exe to msi converters, etc, but cant seem to find a solution. why does it have to be so hard to just change a setting in a application....jeez. most likely i'm gonna be giving up entirely on testing any of the odyssey clients unless someone here can be so kind to just edit the applications and re-upload the modified exe or msi package asap so that i can at least install it on windows 95 for me to test. the site of upload is here "https://easyupload.io/". also i don't know if one of these programs caused viruses but i faced a new problem i think, where the exe file wont even run / install on my w7 system ( other programs do, just not the odyssey client 1.1 / 2.2 ones ). here is the 2 clients if anyone can modify them and re-upload to the same site - https://easyupload.io/pnhbei
  6. so i didn't realize, but the 3 clients are apparently not msi executable based, they are just regular .exe. do you know if there is any tool similar to orca that can do the same thing, bypassing the operating system check that is?
  7. i was trying to see if i could install odyssey client 1.1 or odyssey client 2.20 oem edition on windows 95, but unfortunately the installer gives the error "error 3031,Odyssey server requires windows 2000 SP2 or greater, Installation will abort". i was wondering, is there any workaround for this. i remember people mentioning a registry modification that involves changing the productname/version numbers, and then the programs would install and work properly. i tried to google myself on windows 2000 product name, but i couldn't get far in a feasible scope, all i managed to get was one thread here on msfn, i had entered the productname and version of windows 2000, but it still didn't make a difference, i even changed another entry that originally was windows 95 and changed it to windows 2000. the only other way i can think of is using this orca modification tool mentioned from the site below, the steps do not seem to be very difficult, just edit, save the file, and i should be good to go. but i was wondering if anyone has had any experience in using the orca tool and / or other ways to be able to get all this working? i already messed up my registry a bit and going back to the normal changes, i dont have the original info, but with the orca route, it seems that it bypasses all that stuff so the previous registry changes wouldn't matter. i will be re-installing the os anyways, however, i really need to at least confirm these methods as working or not, and if not, move on to another wireless client that does. http://david-merritt.blogspot.com/2012/08/force-blocked-software-to-install-onto.html
  8. i downloaded the windows 95 osr 2.5 version with microsoft plus integrated, however, after the "Typical" installation choice, it does not appear to install it, at least, when i checked the wallpaper part, it did not give me the option to stretch the screen. i tried to see if i can add new programs, but i couldn't find any relevant option. i installed the desktop wallpaper item, but it didn't add the wallpaper stretch option. i want to be clear that the main if not only reason i need the microsoft plus package is so i can have that added wallpaper stretch option in the system properties display window. i tried some file a little while back from the internet that was some kind of registry entry that was supposed to add the option for wallpaper stretching, but it didn't do anything. i don't wan't to add the entire microsoft plus package to my archived package if i don't need to, is there any way i can add the wallpaper stretch option in a easier way or perhaps something i'm missing from installation?
  9. there was a thread that sdfox7 mentioned on the 0.8.x family being the last that doesn't depend on SSE, he mentions in this thread below:
  10. there is some slightly different methods / options you can try. first, use no more than 512 MB of system ram upon installing and early configuring, 256 MB may be even more suitable. also, to be sure you're using the latest / "best" versions of fix95cpu, as well as 98SE boot disk. i have uploaded them to the easyupload site. you can download them from here "https://easyupload.io/4gv4ya". the boot disk is a slightly modified version, i don't remember the exact changes, i even did them myself manually, i think it's ms dos 7.1 based and accompanied with some other fix that allows better partition sizing ability. for the fix95cpu one, it's version 3.0. there is some additional info i'll want to give you if you do get a successful setup. below is an instruction set i created that would apply for clean install of windows 9x. i would use the "setup /p i" command ( mentioned below, as your chipset is ich5 ) . put in 98SE boot disk in optical drive and allow it to load or be selected from boot options . boot from cd rom, when the start up menu appears, select start computer with cd rom support . go to fdisk by typing fdisk in the command prompt and select yes for large disk support . clear all partitions that are not needed or create a specified partition and make it active after it you created the exact size . reboot, put back 98SE boot disk and make sure fdisk has the specified drive active . exit from fdisk and now that you are back in command prompt, you should be able to go into either the "d:" or "e:" drive . for custom builds that do not use the original windows cd, the optical drive directory will be most likely "e:" so type in "e:", then type "cd win98", or if it is windows 95, type "cd win95", it should then read "e:\win95" or "e:\win98" . you can then go ahead and type "format c:", press "Y" . then after format completes, press enter and then type "md c:\win98" or "md c:\win95" and then press enter . then type "copy *.* c:\win95" or "copy *.* c:\win95" and press enter, this will copy install files to "c:" drive . then you can change to the "c:" drive and run setup by typing "c:", press enter, and then type "cd win98" or "cd win95" and press enter . then it should read either "c:\win95" or "c:\win98" and you can then type "setup" and press enter or a different command of setup depending on the system, some systems may require running a certain setup switch such as "setup /p i" . the setup should now load and should not need the cd anymore unless specified, i like to keep it in for the first setup phase and remove it right after the 1st phase restarts, for windows 95, some systems with fast processors such as pentium 4 will need you to load fix95cpu version 3.0 right before the 2nd setup phase to allow fully installing of windows or else a windows protection error occurs, this update also fixes other things
  11. it would help to know your detailed specific system specs. motherboard / computer model, how much memory is installed. the patch needs to be installed right before the 2nd installation / setup phase or right after the 1st setup phase, insert the fix95cpu version 3.0 disc and allow it to load on next reboot. also, make sure that the windows 95 installation is a clean install.
  12. does the 82.69 driver also support pci express based cards on windows 95 or is it only for agp based ones?
  13. so i'll take that as a yes that it will install on windows 95 and can make use of more than one core IF there is application that was made to use more than one core at a time? ( not to be confused with hyperthreading which i believe the MULTCORE SDK does not make use of / and ignores it )? for me, that would be all welcomed, as i despise hyperthreading . disabling it is the number 1 thing i'd do. do you know any programs that can disable it in the OS for w9x? i mean, it doesn't seem like 9x systems even notice it, but let's say there was a program that works on 9x - xp to disable hyperthreading in xp, do you think it would have any effect whatsoever on 9x or overall, maybe less heat and less power consumption, because the cpu isn't doing something else for no reason?
  14. how exactly do you install the "user-agent-switcher-0.6.10-bump.xpi" extension? do i just copy it into one of the folders of the already installed retrozilla program files folder?
  15. i would think that if if compiled or developed properly from / for the w9x level, then it would allow forwards compatibility, but not the other way around. but for me, i simply had a nostalgic / unique project idea that involved developing or contributing to a mmorpg that could work on as old as windows 95 / 98, to as new as windows 10, and milkshape 3d 1.8.4 would be able to offer some of that support, although it only works on 98 or newer, where as milkshape 1.6.6a works on windows 95. i would be fine using 1.6.6a, so as long it can do most of the things necessary to complete / or contribute to the unique project. i'm not a programmer in any shape or form or coding, nor would i want to, but if i could be participating in the artistic / feature elements of the project such as creating certain textures / and stuff within milkshape, then that's where my interest would lie. i'm optimistic that the hardware part would be sufficient to handle such a game, as now you have rloew's patches, etc. with a system that has let's say 1.5 GB - 2 GB of ram, pentium 4 cpu at 3 Ghz or so or perhaps core architecture, and 256 MB - 512 MB graphics card, then it would be able to do run the game well and it would look decent. i know i may have my head in the clouds with this idea, and that's fine, but i was really looking at people who'd share the same interests as i do for this, as that's obviously one of the first starting points.
  16. if file size is not too important, then vlc player 1.1.9 should work well as the last officially working, assuming you're using a cpu that uses SSE2 or newer ( i think from 0.8.6e and newer, they require SSE2 based cpus?, but i don't know if this is true or not ). i use vlc player 0.8.6d on windows 2000 because it seems to give a good balance by supporting older SSE only based cpu but also being modern enough to do work with most files and have decent quality and reliability, though a large part why i use 0.8.6d is because with version 1.1.9, the size of my archived package would then become a bit large, possibly preventing me from burning onto cd-rw / cd-r discs that can only do a max of like 677 MB or so ( i can't really remove anything else ). i don't see a reason to use newer than 1.1.9 unofficially, but that's a route you can experiment with if you use some kind of unofficial update rollup / extended kernel configuration. sorry, i don't have experience with the other things you mentioned. below is a link for vlc versions you can download - http://download.videolan.org/pub/videolan/vlc/
  17. to create a usb bootable windows 2000 sp4 image. the method below may or may not work, and if it does, the installation part may still have issues, but this is what i wrote below for myself to do it, ( some things may not be correct, so you may have to do some tinkering of your own, as i have not tested this method for a very long time, and it was only for regular windows 2000 sp4 iso, not modified / nlite ones ), also you'll need to have already made a updated windows 2000 sp4 image using the above fixes i mentioned in my previous post FIRST, then go along with the instructions below: youtube video instructions- https://www.youtube.com/watch?v=cNJ_xzJMTcQ website to download the usb tool- http://www.winsetupfromusb.com/downloads/ steps in text: -have windows 2000 sp4 iso downloaded -open up the winsetupfromusb tool, version 1.8 works with filename of "WinSetupFromUSB-1-8.exe" -click rmprepusb for the usb device selected -check the xp/bartpe bootable ntldr option, ( works for windows 2000, even though windows 2000 is not listed in this section ), check NTFS for faster burning / etc, check boot as hdd ( c: 2ptns ) -then click prepare drive and then ok, then ok for erase all data -then extract the windows 2000 sp4 iso into another folder -copy the folder of the extracted files of the windows 2000 sp4 iso into the add to usb disk section for windows 2000 -then click i accept for the pop up window, then check QEMU, then click go -then it should give a job done window, click ok and safely eject usb and you are ready to install 2k from usb
  18. i've only used windows 7 or windows 10's default burning feature for discs ( using the mastered burn option to allow working on most computers ). if you're trying to burn the iso image onto usb, i'm not sure if i can help you with that ( i'll look into it though and may provide a solution in a bit ). as far as the other stuff goes, i put a download link of the specific driver package for intel ahci / raid drivers below that i slipstreamed with: https://web.archive.org/web/20190502225349/http://w2k.flxsrv.org/cgi-bin/dl.cgi?file=iata76_cd2kh.cab all you need really is the driver files found in the iata76_cd2kh/winall/driver folder. select multiple driver folder / textmode drivers options, as well as bootable iso. for amd, i believe i used the driver found in the link below, make sure to use same method and do not include any x64 drivers - https://web.archive.org/web/20190503144058/http://w2k.flxsrv.org/cgi-bin/dl.cgi?file=ati1208raid2k.cab also, i uploaded the updated USB.IN_ file that MIGHT allow correct installation of usb on certain newer systems, up to intel 2nd / 3rd generation intel might work. USB.IN_
  19. has anyone got wpa to work under windows 95? i found two threads in another forum in relation to trying to get wifi working on windows 95, particularly wpa, but there wasn't as much specific or detailed info of what to do / which driver versions to use, etc. also, i wanted to let others know i tried almost all apps mentioned in this thread, but none of them worked on windows 95, as 98 or newer is required. https://www.vogons.org/viewtopic.php?t=46513 https://www.vogons.org/viewtopic.php?f=46&t=37415 one was using the cisco aironet 350 series cardbus / pcmcia adapter on windows 95 i think ( they didn't specifically state ), but they did mention it being able to connect to wpa, but blue screening at some point. another person "celgen" mentioned using lucent waveland / orinico cards and reflashing their firmware to the gold version to support wep-128, but no mention was made for wpa specifically. "theman" also mentioned "the orinoco gold can be hacked with a newer firmware and drivers which will then support WPA I have a dell version of that card and I did just that... google the hack, it works" but it's unclear on how they were able to get this to work. what was the target OS? what driver version was used, and what firmware version was used and how to do the hack, etc. there's a issue with finding specific hardware id / devs too. i have several packages of wifi devices that do work on windows 95, although some systems may not work due to conflicting cardbus, etc, ( though this MIGHT be fixable by renaming registry entries, etc ), but all unclear, at least for me. it's possible that the lucent / orinico cards, ( including specific silver version(s) ) are rebranded dell truemobile 1150 cards or vice versa. if that's the case, then it might be possible for the hacked firmware route to work. below is supported wireless adapters for windows 95 for dell truemobile 1150 cardbus or mini pci adapter if using only wep. DATE : $Date: 31 Aug 2000 13:45:40 $ $Revision: 1.29 $ %wldel41_LT1.DeviceDesc%=wldel411.ndi, PCMCIA\DELL-TRUEMOBILE_1150_SERIES_PC_CARD-34F2 %wldel41_LT2.DeviceDesc%=wldel412.ndi, PCMCIA\DELL-TRUEMOBILE_1150_SERIES_PC_CARD-C043 also relevant, hermes 1 based chipset cards may have limited support for wpa using odyssey client 2.2 oem edition, however, the readme states 98/ME, but no mention of windows 95. i do not remember if i tried to install this / run it on windows 95. overall, i'm trying to assume a optimistic viewpoint that most of these wireless adapters that do work on windows 95 in just wep, can / and / or do support wpa in either a specific wpa client and / or specific firmware hacked / newer driver. the 2Wire Ruby ORiNOCO PC Card (1000-100016-002) card is hermes 1 based and i think supports windows 95, but it's a matter of finding WPA possibility. i don't know if it's me but i also noticed more stuff missing when i try to google search for them, either the manufacturer's / sites are getting rid of the files or it's a google issue? for example, i can no longer use one of these global ftp file search sites, with error 523? and i can no longer find "AirLancer_11Mbit_Win_95_SR02-2.1.zip", which appeared to be a working windows 95 driver, although for some reason, i could not get it to work when i did test it a while back, despite the package mentioning windows 95. i don't remember if the system files were NDIS3 or NDIS5, where NDIS3 would support windows 95 and NDIS5 doesn't.
  20. for 3d modeling / game design related programs, milkshape 3d 1.6.6a, meshx 2.4, and terragen classic 0.9.43 were all tested working on windows 95. some more information of milkshape 3d 1.6.6a can be obtained in the below link, the directxexp.zip is especially important for directx 8.0 exporting: https://web.archive.org/web/20041109015700/http://www.milkshape3d.com/ms3d/download.html
  21. milkshape 3d 1.8.4 tested working on windows 98SE, as well as meshx 2.4, and terragen classic 0.9.43.
  22. does anyone know if there is a particular time you should be installing the ram patch? like would it be better to install it last, after you already installed all other updates, chipset drivers, etc? at least for 98SE, it appears that it requires certain configuring if installed BEFORE the unofficial service pack, but if you install afterwards, assuming you've taken the right steps in the manual ( can somewhat be different still ), then all should be fine thereafter? like mentioned before, for me, i didn't remove min and maxfilecache settings, it was only the maxphyspage that i no longer use if using rloew's patches on either windows 95 or 98SE. for windows 95, right before shutting off the system to install more ram, i set minfilecache and maxfilecache to 1/24 of how much ram i was going to install, installed the patch, shut off system, installed the desired ram, and it worked fine, but again, when i tried experimenting with min and maxfilecache settings, it caused "Strange" issues, so i believe the cache settings are mandatory, at least for me
  23. i used nlite to do the slipstreaming process. unfortunately i do not have the reference package to check which exact version i used for BWC's drivers. but it was the latest one for amd ( for SB600-800 chipsets, and the h series one ), and also the latest for intel, which i think was last modified in 2018. make sure to also select bootable iso in nlite if you haven't done so. i believe i always used the "multiple driver" option and textmode drivers. make sure to only select the x86 drivers and do not include any x64 drivers as it will corrupt the image / will give you errors in installation. i'm not familiar with the .cab part you mentioned? the universal ATA MIGHT work, despite other people saying it doesn't support ahci / sata / raid or w.e, however, i never integrated that into the package because i thought it would conflict with the intel and amd drivers and / or would be buggy?. so really, it would only make sense to use it in substitute for the amd and intel drivers provided by elsewhere ( BWC / fernando's version(s), etc ). i just used BWC's intel and amd packages because i assumed that it should support all devices anyways.
  24. "oddly" for me, i still need to use 1/24 of system ram for minfilecache and maxfilecache. at least from my testing, i noticed that when i removed the entries, even with rloew's patch, it functioned oddly such as iexplorer.exe causing a illegal operation / page fault, and it usually was related to ole32.dll. another weird issue ( not because of not having the filecache settings ) was with using a older version of vlc player that was able to launch successfully, i don't remember the version as i deleted them shortly after, i think it might have been 0.5.3, if not that, then .4 version that launched, and played a mpeg video shortly before making some weird slight high pitched noise and then exited and complained about a invalid page fault in directx.S0. i don't think the vlc player .8.6d in specific is related at all to system settings or hardware, as i noticed when it tries to install, it mentions not being able to load a certain file ( this happened on other computers ), but oddly, older versions don't seem to have this specific issue, yet still don't run properly. the TCPMP mod player worked fine of brief testing, and i also tested winamp 2.95 without issue for a sample mp3 file. another strange but new issue i encountered was wmi9x failing to load certain files, cimwin32.mof, msi.mof, etc. perhaps these issues might be related to ACPI in some way? also, the reason why i mentioned the 1/24 ram and filecache settings is because without minfilecache and maxfilecache settings of 1/24 of ram, wmi9x wouldn''t even install, with GLB6362 causing a invalid page fault in ole32.dll. i then added minfilecache=86000, and maxfilecache=86000 ( having 2048 MB of ram installed ), rebooted, and was able to install wmi9x, but with the errors related to not loading cimwin32.mof, etc. there was also a invalid page fault with a certain version of vlc i tested, possibly 0.6.2, but instead of it being for ole32, it was mentioned in module <unknown>. so other than wmi9x and those vlc players, i don't think i had any other large issues, at least presumably, i believe the explorer errors were cured from using the appropriate minfilecache and maxfilecache settings, but how other people can run their systems fine without it, i don't know. ironically, for maxphyspage, i did not add the entry in this build, but what are the chances that this would have any effect on the related problems i have? i may need to test this out, despite rloew's patch notes mentioning ( at least for 98SE ), for it be removed from system.ini settings, though not specifically mentioned for windows 95. as for patchmem itself, i'll pass on that information to the next configuration to run patchmem.exe /m. however, i was wondering, for the part he mentioned to copy patchmem to the windows folder, is it ok if it's copied to the c:\windows folder? also what's the difference between using that switch command vs just double clicking the executable? reason why i ask is because i didn't use the switch method, i simply double clicked patchmem.exe to install from c:\windows where i copied to.
  25. the cpu is pentium m, so no, it would not be from that reason, as it supports SSE / SSE2 / MMX.

  • Create New...