jds
Content Type
Profiles
Forums
Events
Posts posted by jds
-
-
Quote
I know I'm late with this, but I think the best option would be going with an external firewall (basically a tiny, Intel NUC-like, PC with UTM software running on it, acting as a pass-through filter between the internet and the home network), outsourcing the antivirus work to a separate machine.
Thanks for the suggestion, but it doesn't fully solve my problem. I also need to be sure flash drives, CD-ROM's and floppy disks (yes, I still use them occasionally) don't introduce any nasties. :-/
Joe.
0 -
On 12/7/2020 at 8:20 PM, jds said:
... I was able to fool and install Avast 9.0.2013, but now the problem is that this needs the VC++2010 redistributable package (edit: actually, it turns out it needs the VC++2012 runtime) for W2000 to be able to run ...
OK, thanks to blackwingcat's VC++2012 runtime (and extended kernel and NNN4NT5), I was able to get Avast 9.0.2013 both installed and "running". Unfortunately, some of Avast's "shields" could not be enabled, so actual protection was lacking.
So I then tried other versions of Avast 9.0 that I could find, but all I could now get was the error "The installer is unable to initialize early avast! self-defence with error 0x0000007f! Aborting!". Even trying to re-install the previous version 9.0.2013 gives this error message! Some research on this error (albeit with different hexidecimal codes) suggested the avast utility "avastclear" could resolve this issue, but so far, no success trying several versions of this utility (some run OK and say that uninstallation was successful, but the same error persists when trying to install Avast 9.0.xxxx).
Joe.
0 -
On 12/16/2020 at 10:00 PM, blackwingcat said:
This component is too old.
It collides against extended kernel.
You don't need it , If you installed extended kernel :3
Oh, that's unexpected. Thanks for the caution, BWC.
Would re-installing your extended kernel after installing the VC10 runntime fix these "collisions"?
Joe.
0 -
On Tuesday, 8 December 2020 at 7:19 PM, blackwingcat said:
Yes, my server moved to http://win2k.org
Thanks BWC.
However, perhaps I don't really understand, as I can't get this to work. I first go to your blog article 1192179, copy the link there for the "vcredist_w2k.exe" file, substitute the server name in the link, but then I get the message :
"",
File not found in List.
Report to BlackWingCatSo, what am I doing wrong?
Joe.
PS. OK, figured it out :
1. Ignore any links in the blog
2. Go to win2k.org
3. Click Windows Legacy Update
4. Click English
5. Click Manual Update
6. Search for "vc" (or whatever, without quotes)
7. Download from the results list ...0 -
On 12/7/2020 at 2:58 AM, jds said:
Well, I've done a little experimentation with this, but am unable to install Avast 9.0.xxxx (the oldest Avast still supported with updated definitions), which complains it needs XP as a minimum. How do I trick the setup program that it is running on XP?
The W98 KernelEx had a compatibility setting in the Explorer file properties window to select the spoofed version, but I don't see this feature here.
Joe.
OK, I've found the answer to this particular requirement. Blackwingcat also released a package called NNN4NT5 (NNN4NT5.cab, MD5=f42020182e6e17cb72ea38ee193ee3d0) which allows temporary spoofing of XP (and some other versions of MSW). It does however include a warning to reset to the correct version before shutting down or rebooting, lest you not be able to boot up next time!
With this I was able to fool and install Avast 9.0.2013, but now the problem is that this needs the VC++2010 redistributable package (edit: actually, it turns out it needs the VC++2012 runtime) for W2000 to be able to run ...
Joe.
0 -
11 hours ago, dencorso said:
Hey! Good to see you! It's been a heliuva long time no seen, or what? Great to have you around!
Thanks, Den.
Good to hear from you too!
FYI, since Avast became non-viable on W98, I "upgraded" to W2000, but haven't used my desktop much since then. Mostly due to lack of time, but also because this O/S doesn't work as well as W98, especially with all my DOS applications. Now Avast has dropped support for W2000, so I need to resolve this or consider Linux+Wine ...
Joe.
0 -
On Wednesday, 25 January 2012 at 9:19 PM, blackwingcat said:
Hi BWC,
Is there a new location where this VC2010 redistributable package for W2000 can be downloaded? The link here seems to point to a defunct server.
Joe.
0 -
Well, I've done a little experimentation with this, but am unable to install Avast 9.0.xxxx (the oldest Avast still supported with updated definitions), which complains it needs XP as a minimum. How do I trick the setup program that it is running on XP?
The W98 KernelEx had a compatibility setting in the Explorer file properties window to select the spoofed version, but I don't see this feature here.
Joe.
0 -
On 6/27/2012 at 4:20 PM, jumper said:
Hi jumper,
These links to posts no longer work, due to syntax changes at MSFN. For the first one, "page__view__findpost__p__1028960" at the end of the URL needs to be changed to "?do=findComment&comment=1028960". The other two similarly.
Joe.
1 -
FWIW, i have 'dbghelp.dll' version 6.0.0017.0 (DbgBuild.020528-1721) on my system. I think it came with Real Player 6.
Joe.
I can't install new Foxit Reader 6.0.2.407. Message: "Runtime Error (at -1:0) Cannot Import dll: C:\Windows\Temp\...\FXCUSTOM.dll"
But there is a possibility to start and run it. I installed it on XP SP2 (SP1 isn't enough), copied the Foxit program folder onto the Win ME desktop. The Foxit Reader.exe needs Kstub822 with following definitions
[KERNEL32.dll]
ReleaseActCtx=z1
CreateActCtxW=p1e0
ActivateActCtx=o2e0
DeactivateActCtx=o2e0
to start. Better run it with comp.mode XP.
The ImportPatcher complains about jrsysMSCryptoDll.dll and imgseg.dll, too. The jrsysMSCryptoDll.dll is located in the plugin folder.
Printing isn't possible anymore. => The DBGHELP.dll of ME is too old. Upgrade required.
As a reminder: I'd installed already MSXML 4.0 SP2 for version 5 and I've the winhttp.dll of XP in my system folder.
Now I've successfully installed Foxit Reader 6.0.2 0413 and 6.0.3.0524 with an additional entry.
[WINSPOOL.DRV]
XcvDataW=z8e
Also Required:
[KERNEL32.dll]
ActivateActCtx=o2e0
CreateActCtxW=p1e0
DeactivateActCtx=o2e0
ReleaseActCtx=z1
winhttp.dll
msxml4 SP20 -
Thanks, Den!
I've been travelling ... now I'm playing catch-up ...
Joe.
0 -
Not me (in answer to the original question).
Perhaps RapidDriver (shareware) from www.entechtaiwan.com is a possibility.
According to the scant history log :
09 May 2006 v=2.1.4.11
- Windows 98 installation bug fixedSo the last W9x compatible version (demo) may be : http://web.archive.org/web/20060718184622/http://www.entechtaiwan.com/files/rdeval.zip
OTOH, maybe even the current version is compatible, just not officially. At worst, it may require the assistance of WDMStub (search for the thread in this sub-forum).
Joe.
0 -
Not sure how much help it will be but, at minimum, Windows Management Instrumentation will need to be running:
http://support.microsoft.com/kb/322363
Note there is a section for 98 and 98 SE.
You *may* also need DSClient:
http://www.imss.caltech.edu/node/414
This page has a link to the setup under the section 'Where Can I Get The DSClient?'
I think there was hotfix for this at some point in time.
Edit:
Should've figured:
Yes, you are correct. The original error was resolved by installing WMI. I don't know if DSClient is also needed, as I have that installed already for other stuff anyway.
After resolving this first VBS error, I implemented a couple of work-arounds for subsequent script errors, as below :
ASCII differences between ORIGINAL.VBS and MODIFIED.VBSReplace lines 201-208 in ORIGINAL.VBS< For Each oProc in oProcs< If Instr(1, oProc.CommandLine, WScript.ScriptName, 1) > 0 Then< If bFound Then< WScript.Quit< End If< bFound = true< End If< Nextwith lines 201-208 from MODIFIED.VBS> ' For Each oProc in oProcs> ' If Instr(1, oProc.CommandLine, WScript.ScriptName, 1) > 0 Then> ' If bFound Then> ' WScript.Quit> ' End If> ' bFound = true> ' End If> ' NextReplace line 261 in ORIGINAL.VBS< sLocalAppDir = oFso.getFolder(oShellApp.Namespace(&H1c&).Self.Path).ShortPathwith lines 261-262 from MODIFIED.VBS> ' sLocalAppDir = oFso.getFolder(oShellApp.Namespace(&H1c&).Self.Path).ShortPath> sLocalAppDir = "E:\Progra~1"
Now what seems to happen is that the script produces one or more temporary sub-directories in the Zimbra installation directory in "\Program Files\Zimbra", whose contents are deleted. However, there seems to be a problem with the way it determines the path of these temporary directories, so that it also ends up deleting the contents of the whole Zimbra installation directory.
That's as far as I've managed to progress this thing so far.
Joe.
0 -
Due to extremely poor performance with the newer MS servers, I had a look around for a potential replacement for Outlook (2000 and XP versions, both are terrible). The one that seemed most complete, including support for Exchange Server, was Zimbra ...
OK, so I downloaded the file 'zdesktop_7_2_2_ga_b11951_20130318071431_win32.msi' (MD5=9bfac177eba208553ae2940f92befe9f) and proceeded to hack this XP+ package as follows :
1. Open in hex editor and at address 5A85FCC, change 2C 01 to C8 00 (surrounding bytes = 01 03 00 00 00 2C 01 00 00 03).
2. Open in Orca and delete the VersionNT check line in 'LaunchCondition'. Save (don't use Save As).
3. Run the MSI.
4. In "\Program Files\Zimbra\Zimbra Desktop\win32\jre\bin" rename 'plugin2' directory to 'plugin2_inhibit'.
5. Copy 'cscript.exe' from "\WINDOWS\COMMAND\" to "\WINDOWS\SYSTEM\".
OK, now Zimbra Desktop is pretty much installed. It has few dependencies beyond what W98 provides, and KernelEx can probably provide the rest.
However, it is launched by a VBS script called 'zdrun.vbs' and that gives the following error at line 250 (copy the shortcut command and run from a command prompt to see the error) : "Microsoft VBScript runtime error: File name or class name not found during Automation operation:'GetObject'". Trying to run the Zimbra executable directly just produces an error message about a missing configuration file, so presumably, that is supplied by this script.
So, is anyone familiar with VB script ... ?
Joe.Edits : In step 1, eliminated first byte of the surrounding context (can be used to find equivalent patches for similar MSI files, such as earlier versions of Zimbra). In step 5, changed edit of Zimbra shortcut path to a file copy of 'cscript.exe' instead (solves other instances of the path issue).
0 -
Another Bluetooth stack that I've heard about is the Toshiba stack. It used to be available from Roving Networks, but as it was hosted on an FTP server, it's not available from the Internet Archive ...
The only place I've found it is here : http://gridconnect.com/bluetooth-usb.html (click on the Documentation tab)
It's a ZIP of the BluePlug Product CD, which is why it's a whopping 325MB (most of that bulk is due to multiple stack copies for various languages). It contains V3 of the Toshiba stack, which is W98 compatible, also V5, which is said not to be compatible, plus some other stuff.
As with the Widcomm and IVT stacks, this one also looks to be generic in nature. (BTW, for some of the newer device VID/PID information, have a peek at the V5 files.)
Joe.
0 -
There definitely is a Bluetooth driver that works in 9x. I had one driver package from a BT dongle installation mini-CD, then I found (maybe mentioned here in these forums?) two other rather huge packages (35MB and 62MB, respectively) that were distributed by D-Link and Emtec. All of these packages contain an inf with a long list of vendor and product IDs and software produced by Widcomm.
I think these are the pages where you can download the above packages :
http://www.dlink.com.au/tech/download/download.aspx?product=DBT-122&revision=REV_C&filetype=Drivers
Now for the IVT BlueSoleil stack ...
Firstly, there's version v1.4.9.4 of the IVT BlueSoleil package included in the Emtec package above.
Then, there's version 1.6.4.0 x64 Beta 050920, as provided by Swann Security (for the now discontinued SW120-BTA dongle), available here : http://www.swann.com/downloads/drivers/bluetooth/
Joe.
PS. Beware that as Drugwash has mentioned, most (if not all) IVT packages default as "crippleware". Without a registration key, they are apparently limited to transferring 2MB or 5MB of data.
0 -
Following on from the sub-thread here : ...
There are some Bluetooth devices that support Windows 98. They may have useable Drivers.I may have found something useful, by searching WIDCOMM drivers, prompted by your suggestion. Here are some potential candidates to test. The XP WIDCOMM Bluetooth Stack can be made to accept almost any Bluetooth Radio by editing the .inf, in the same way as we do with NUSB on 9x/ME, so perhaps one or more of those 98 WIDCOMM drivers can be turned into a general solution...
At present, I only have one Bluetooth device (USB adaptor) , by connectBlue, and that has an internal Bluetooth stack, so the only driver it needs is the FTDI USB-Serial driver. However, I have recently ordered some cheaper devices on eBay, which I assume will not have an inbuilt stack, so then I'll be needing to try some W98 stacks.
The Widcomm stack (linked above) does look fairly generic, and I have found another (slightly newer) one here : http://web.archive.org/web/20070304132823/http://www.rovingnetworks.com/bin/USB-BU2050.zip
PS. Two more (one even newer) Widcomm exemplars :
There definitely is a Bluetooth driver that works in 9x. I had one driver package from a BT dongle installation mini-CD, then I found (maybe mentioned here in these forums?) two other rather huge packages (35MB and 62MB, respectively) that were distributed by D-Link and Emtec. All of these packages contain an inf with a long list of vendor and product IDs and software produced by Widcomm.
I think these are the pages where you can download the above packages :
http://www.dlink.com.au/tech/download/download.aspx?product=DBT-122&revision=REV_C&filetype=Drivers
http://www.emtec-international.com/en-eu/old_drivers
Joe.
0 -
Hi Joe,
I wonder if installing the Service Pack would help me.
Basically, I followed these instructions:
http://www.bleepingcomputer.com/forums/t/171263/mtp-devices-in-windows-me/
I do already have the MTP support pack installed, and I was also able to successfully install a driver for my phone, i.e. it is detected in Device Manager.
However, unlike Windows XP (and according to the link above, also Windows Me), Windows 98 does NOT show up the MTP device in Windows Explorer. Therefore, I am not able to browse and manipulate with the files on my device. Is there any piece of software that would enable me to do this? Windows Media Player 9 is not helpful.
Thanks!
Hi Ivan,
Well, I don't know if the SP will be of any help, probably not. I don't use it as the current maintener doesn't care that I don't want to mess around with my drivers, which took so much work to get working properly, or that the Adaptec ASPI layer update breaks my scanner. It has gone far beyond the scope of an SP and bundles other packages that don't belong, typically giving you no option about installing them.
Anyway, if you "drilled down" the link I gave you, you would find my notes on my initial experimentation with MTP/PTP. I concluded :
So, with 'MTP9x-2k.exe', 'wpdmtp_sample.inf', 'wmdmcmd.exe' (and 'readme_wmdmcmd.txt'), you have rudimentary support for PTP/MTP devices in Win98/SE/ME. Install 'MTP9x-2k', make an INF file for your device using 'wpdmtp_sample.inf' as your template (use 'usbview' to find the appropriate PID and VID values), then use this to install the device driver. Finally, use the (rather crude) 'wmdmcmd' utility to copy files to/from your device, etc. (hint, 'wmdmcmd' can operate in command-line mode, so you can take advantage of the command-line editing features of 'doskey').
Joe.
0 -
BIOS is there in the link. A program to test 48-bit capable exists. 150 ≠ 200, so
(the "implied" reason I gave the link and recommendation of DOS-based)..."150 ≠ 200" is the reason I said FWIW. However, the respective dates are encouraging :
Dell OptiPlex System BIOS, A05
Optiplex GX200 A05 FlashBIOS
Release Date: 18/08/2003
Dell OptiPlex System BIOS, A11
Optiplex GX150 A11 System BIOS
Release Date: 2/1/2005
Joe.
0 -
Perhaps this can help? :
Joe.
0 -
PIII or Celeron (probably the last Socket-370 version) - Intel 815E - PC100/PC133 SDRAM. Doubt if 48-Bit capable...
FWIW, my similarly spec'd GX200 is supposedly LBA48 capable with the latest/last BIOS update (A05 if I recall).
Joe.
0 -
What happens if you type at the command line? : win
Joe.
0 -
Thanks for the link, I used the link and ran wdmcheck. Only one missing function with wnihdd50.sys file: "mmisaddressvalid" . With wnihdd51.sys, the list is longer. Is there a stub for this?
Yeah, someone would need to rebuild 'wdmstub' with this function/stub added ...
Here's an interesting driver with at least a W98-supporting INF : http://cache-www.belkin.com/support/dl/f5d8000.exe
Unfortunately, it lacks the W98 SYS file, as described here : http://www.broadbandreports.com/forum/r17282846-Belkin-F5D8010-pre-N-laptop-card-missing-drivers
I don't wanna get too far off topic, but I did find this while looking. I know it's not what you're looking for. I never saw it before, says it compatible with 98 SE or later:
Not too far off topic? (Rhetorical question.)
Joe.
0 -
It sure does seems like Oracle is doing a one last farewell tour for Java SE 6
This is at least 3 times they have promised the end, so we should start a pool on this.Yeah, they've even been keeping version 1.5 up-to-date, but only for paying customers : http://www.oracle.com/technetwork/java/javase/documentation/overview-137139.html
That's what's been promised to happen to version 1.6, hopefully they won't do this until all the major security holes are plugged.
Joe.
0
Hey! Good to see you! It's been a heliuva long time no seen, or what? Great to have you around! 
(the "implied" reason I gave the link and recommendation of DOS-based)...
This is at least 3 times they have promised the end, so we should start a pool on this.
KernelEx for Win2000
in Windows 2000/2003/NT4
Posted
Well, the only progress over these weeks has been with regards the "The installer is unable to initialize early avast! self-defence with error 0x0000007f! Aborting!" error. If I re-install the earlier 8.0.1497 version, I am able to "install" most 9.0.xxxx versions over this (with the help of NNN4NT5) without errors. However, the "shields" are down and actual protection is lacking (the Avast service, I think it's also called).
Joe.