sleffing

Member
  • Content count

    25
  • Joined

  • Last visited

Community Reputation

0 Neutral

About sleffing

  1. Have you tried winpack.org ? Also search this forum for "sp2 localization". You will find many posts by Petr like Localization of SP 2.0
  2. submix8c has good ideas. You might try Craig Hart's PCI .. http://members.datafast.net.au/dft0802 If you haven't. (The unleaded version not pci32.)
  3. A .pif file is sent SFN. A link to Start.exe creates a .lnk file -> passed a LFN. Also links to vbscripts (.vbs files) are passed LFN's. If vbscript is available on the target create a link to a .vbs file. W98 will pass LFN always..even as a .lnk file in the sendto folder. Simple vbscript to RUN your bat - save as c:\temp\tmp.vbs - WScript.CreateObject("WScript.Shell").Run "C:\TEMP\TMP.BAT " & WScript.Arguments(0), 1, FALSE For a test - c:\temp\tmp.bat looks like this: @ECHO OFF ECHO %1 %2 %3 %4 %5 %6 %7 %8 %9 Note tmp.bat still sees the command line as separate pieces when spaces are present in the path/filename.
  4. Hi Sfor. No VNC help but, I can confirm no visible support for 24 bit colordepth in Intel 82845G (driver version: 4.14.10.3732) (see Mijzelf's comment). I have a dozen or so of these in the form of Dell Dimension 2400 desktops all running W98SE. Also 2 resident programs come with the default driver install..set to run @ startup via HKLM/run. A tray icon (igfxtray.exe) and a hot hey monitor (hkcmd.exe ?). These can be enabled/disabled thru the ui - right click Desktop ->Graphics Options But they are already resident so best testing may require disabling them thru msconfig & reboot. Last, I had initial issues with the display resolution spastically reseting to 640 X 480 on bootup. I ended up setting a forced configuration for the video adaptor in device manager. This to avoid the memory conflicts. Check device manager for that as well.
  5. Most use an inf file. MDGX gives a good example. Go here: http://www.msfn.org/board/98-fe-98-se-me-u...xes-t46581.html Scroll down to the updates from 2-25-2009. Or just search for "ieakb". Download that days ieakb patch and use it as an example for yourself. This particular patch from M$ is cumulative and where MDGX's old version leaves off will have been added to toward the end of the M$ patch you already have. MDGX's inf for this patch is about the simplest form of inf file (just the nature of the patch) and so it's a good starting point if you have no experience. Good Luck.
  6. Craig Zacker still has this book online: Building Windows 98 Networks. The first few chapters cover the basics, chapter 6 is where it really gets interesting.
  7. The file your looking to replace/rollback is avgabout.dll. You want version 7.5.0.556. AVG makes a backup at each update. If you are lucky you will find the file at: C:\WINDOWS\All Users\Application Data\Grisoft\Avg7Data\avg7upd\backup (The location on my system.) I copied back avgabout.dll & avg7US.lng. This is probably a language specific file and may have a different name on your setup. Thing is if you have automatic updates enabled those will be replaced next update. The definition updates listed here still work for me. http://free.avg.com/download-update I just download the 2 files with "avi" in the file names and use the manual update option in avg pointing it the folder I download the updates.
  8. Thanks Gape. This is coming together. I installed the MAIN updates only here. This system is an old installation. PPPMAC.VXD is still an issue on systems with netbios networking. I got a 'windows file protection error' on reboot. Replacing pppmac.vxd got past that. There's a new ROOTSUPD version available. I had version 17,0,2195,0 and the sesp replaced it with version 16,0,2195,0. Those apparently will overwrite an older version. I did not know that. Along the same lines.. deleting the CryptoSignMenu key probably works fine in spupdate.inf but it is added right back in by some subsequent action. This didn't show up in a regshot at all. So it must be added back in during 1 of the RunPost sections and before the install completes (and before a reboot). Dunno. Other than that. I replaced the windows only version of EXTRACT.EXE provided in the service pack with 1 that works on my Emergency Boot Disks. That is my personal preference. Thanks again. Your time and work are much appreciated.
  9. That is from win2K SP4 (W2KSP4_EN.EXE).
  10. Thank you sir. Now it is complete.
  11. Success! Thanks. I don't know if the CRLUPD.CAB gets applied. OH NO! I strongly disapprove of this, Gape. BOTH the 2_4DATE.EXE file AND "sShortDate" are needed to make ALL programs that have date functions use the "m/d/yyyy" format. The "sShortDate=M/d/yyyy" in WIN.INI is used by 16bit programs like File Manager (WINFILE.EXE). File Manager does NOT use the date format settings from the Windows registry. While the 2_4DATE.EXE file only updates the Windows registry to make only 32bit programs like Windows Explorer use the m/d/yyyy format. 2_4DATE does NOT make 16bit apps like File Manager use the 4-digit year date format. That's why "sShortDate" is still needed. So you will need to put back WIN.INI sShortDate into the next beta release of the 98se SP. @Gape... Do the whole 2_4date update or not. It's your call. I use Office2000, Adobe, & other 90's vintage apps on several 98SE computers, all with no problems. All without the 2_4date update. And with no issues I know. -- If anyone doesn't know... Applying the 2_4date update is equal to choosing the Short Date Style - MM/dd/yyyy - in the Control Panel --> Regional--> Date tab. This updates both the registry and win.ini. --
  12. @maximus-decim Thanks for the update. It woks for me. But, I found this in my registry after installing. [HKEY_LOCAL_MACHINE\Software\Microsoft\Updates\DataAccess\%COMPID%] "%COMPID%" ? I found some other similar issues. [HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer\ActiveX Compatibility\%KillBit_GUID%] I tracked it back to OTHER.INF. These string definitions seem to be missing. All related to KB870669. [Strings] -- ; add these to other.inf COMPID="KB870669" KillBit_GUID="{00000566-0000-0010-8000-00AA006D2EA4}" Package_GUID="{5f3c70b3-ac2f-432c-8f9c-1624df61f54f}" SourceDiskName="Microsoft Data Access Components" VERSION="6,0,2800,1106" -- Thanks again. Your work is much appreciated.
  13. A list of localized versions of the 98 SE Service Pack can be found here: http://exuberant.ms11.net/98sesp.html But spanish is not listed, yet. The "recipe" for localization of SP 2.0 can be found here: http://www.msfn.org/board/Localization-SP-20-t44731.html P.S. Many fixes have been issued since SP2 was released. If you find you are interested in making a Spanish version you should use the latest service pack files found here: http://www.msfn.org/board/98-SE-SP-30-BETA-1-t61749.html
  14. Microsoft has issued an update... "December 2007 cumulative time zone update..." dated 11/27/2007 http://support.microsoft.com/default.aspx/kb/942763 And MDGX has has followed suit with an update for W9x users dated 11/07/2007. http://www.mdgx.com/add.htm#TZU Thanks for that but I have 3 issues. The "AUS Eastern Standard Time" TZI info needs to be updated to the "2008" data. The "Cen. Australia Standard Time" TZI info needs to be updated to the "2008" data. The "Israel Standard Time" is screwed as well. The information for Israel on the M$ web page is wrong too. Particularly the "Dynamic DST" info. So I suppose the standard channel updates are unreliable as well. Please use this TZI data for Israel in the year 2008: TZI,1,88,ff,ff,ff,00,00,00,00,c4,ff,ff,ff,\ 00,00,0a,00,00,00,01,00,02,00,00,00,00,00,00,00,\ 00,00,03,00,05,00,05,00,02,00,00,00,00,00,00,00 Tasmania, Egypt and others are already updated for 2008. Look up any time zone info here: http://www.timeanddate.com/worldclock/ And I found this. Yearly Reg files posted here for Israel: http://www.lingnu.com/support.html#timezone
  15. Gape, Thank you for the massive effort this must take. I test installed/uninstalled the logos. I installed the LOGO update by itself. Unchecking all else in the installer. An error like 'rootsupd.inf is not found' popped up. I dismissed the error box and the logos installed, backed up and all was good. ------- So I went to uninstall the LOGOS from add/remove and had an error...not the same as you, though. It went into a loop. No error boxes. I hit ctrl-alt-delete and killed 1 of the many instances of rundll. That stopped the looping and the uninstall finished without further error. It did create a bunch of entries in advpack.log and 100 or so randomly named .PNF files in the inf directory. Now that I think about it maybe I would have gotten the error "COMCTL32.DLL file cannot start" if I had waited long enough.