os2fan2

Member
  • Content count

    431
  • Joined

  • Last visited

Community Reputation

2 Neutral

1 Follower

About os2fan2

  • Birthday 07/23/1957

Profile Information

  • Country

Recent Profile Visitors

283 profile views
  1. You can put cc-Cleaner as a menu item on the rubbish bin. This would make room for something more useful, such as 4os2.
  2. Runs on windows 7 too. No need to wait for vista 4.0 (windows 10)
  3. You really need to modify setup.hiv as through my batch file. This is because the full disk needs to be seen by setup, and setup.hiv is the registry here. setup.hiv is the first half of the system hive. Because this represents an inactive windows setup, CurrentControlSet does not exist, and you have to modify ControlSet000 instead. This is what my batch file does. If ye plan to install other drivers, you should use the same controlset000. You don't need to insert any LBA fix into the hive*.inf files, as it is done already in the setup.hiv
  4. I noticed that Microsoft had reinstalled GXP twice since i deleted the original files manually. There has been a number of other memory hogs around too, like their software scanning stuff (compatlogger or something). I found that in procexp, and had to use runasti to get rid of it. The latest version of GXP control panel runs as a service, and does make all of these things that never10 does, and a few more (like actually deleting the apps, which you need to do as a trusted installer.
  5. One has to remember that SxS is a cure for DLL-HELL. DLL Hell arises because Microsoft could not keep a contract. In essence, if you release something like VBRUN100.DLL as a library for VBASIC apps, then any version of VBRUN100 is meant to keep the same published APIs. That's the whole point of it. People write proggies to run expecting VBRUN100 to run. You can, of course end up with the maze of MFC30, where the source code was released for the DLLs, and the individual programmers fixed the code and recompiled DLL files. THREED.VXD is yet another multi-version thing that had to be in Windows directories, but there were just too many of them. The cure for DLL hell was to create a 'virtually in windows' structure, where the individual assembly directory pretends to be in the windows directory for the process that invokes it. This is SxS. Of course, you get programs where refreshes are recompiled in different versions of the same thing, so the implementation of SxS has just made the problem worse.
  6. One might suspect that GWX free update virus is the next service pack for 7, 8, and 8.1. The sad thing is that outside in the real world, downloading three DVDs over ADSL to update three different computers is quite a pain, and actually costs more money than buying one CD-ROM and uploading the stuff locally, even if it has to be validated. From what i have seen of GWX, it seems that they imported people who were more apt at writing virus search engines etc, rather than serious serch packs for Windows.
  7. The SxS crap has to do with microsoft's inability to keep a contract. In essence, if you release some sort of DLL interface, such as 3DCTL, or VBRUN100, then people write programs to interface with these, and you are not supposed to break this interface. So when they started to change the interface, it created a thing called DLL hell. Of course, these DLLs were meant to go into the windows directory, so you can have six or seven different incompatibable versions of the same DLL, each with its own set of dependent DLL files. So was born the DLL MAZE, called assemblies. This maze consist of a nest of directories, each meant to have a matched set of DLLs so that programs can use ver 4.2 of that DLL or 4.7 or 5.0 or whatever, each designed to support a different set of 'run or break' programs.
  8. Until the summer rebuild of the computer last month, the system routinely booted Windows 2000. God I miss it. Currently it's on Vista 6.1 (aka 7). Gave XP the miss. One laptop has windows xp and 7 on it, but 7 has not been fixed for the GWX virus yet. The main boxes have GWX antivirus protection running on it.
  9. Oh yes, you can indeed fire up your favourite reg editor, and like all god-mode things, you can poke your nose into areas normally denied, such as SAM and SECURITY. The more i explore GWX, the more it looks like these browser-extension viruses like bonzo search engines. Autoruns will happily launch the tasks programs, so it seems that it's pretty awesome version of 'power-prompt'. I should imagine that it is the right place to run batches in. CDF (which is my generic W2K batch written around Frank Westlake's 'conset') works. This batch runs under cmd.exe, and changes drive and directory to any named directory in the shell directories, and you can create in registry, your own 'shell-folder' set, so eg "cdf batch" changes to the batch folder. It also can open the registery at the appropriate page so you can have a peek. So i should imagine it's not hard to make a registry entry for 'tweaks', and cdf tweaks, and run your batch files from there. Use regmagik or regjump to handle the reg:hklm thing. Both of them support it. @echo off:: cd shell folder.set zdir=set zshf=Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Foldersif /i "%1"=="/m" goto :hklmif /i "%1"=="/u" goto :hkcuif /i "%1"=="/w" goto :hkweif /i "%1"=="/i" goto :imageset zcmd=chdirset zhere=%*if "%1"=="/o" set zcmd=openif "%1"=="/o" set zhere=%zhere:~3%conset /q /k zdir=HKLM\%zshf%\%zhere%if not "%zdir%"=="" goto :doitconset /q /k zdir=HKCU\%zshf%\%zhere%if not "%zdir%"=="" goto :doitconset /q /k zdir=HKLM\Software\Wendy\Folders\%zhere%if not "%zdir%"=="" goto :doitgoto :end:hklmshelexec reg:hklm\%zshf%goto :end:hkcushelexec reg:hkcu\%zshf%goto :end:hkweshelexec reg:hklm\software\wendy\foldersgoto :end:imageset zdir=Microsoft\Windows NT\CurrentVersion\Image File Execution Optionsshelexec reg:hklm\software\%zdir%goto :end:doitset zcxm=if %zcmd%==chdir cd /d %zdir%if %zcmd%==open shelexec %zdir%:endset zdir=
  10. It's even more interesting. I started "runasti cmd.exe" and this gives me a command prompt. I then use fcw to find the GWX files as above. I then run autoruns.exe (Sysinternals), and kill all of the GWX proggies out of there. It says it can't find the EXEs. From GWX control panel, the program can't even find the EXEs. The system boots nicely, and it is no longer a case of 'you are allowed to run your system between updates"
  11. I ran runasti on my vi.6.1 32-bit system, and got it to run cmd.exe. From this cmd.exe session, I launched programs, like fcw.exe (a File Commander/W, a port of an OS/2 program), and change to the gwx directory (\windows\system32\gwx). I renamed all the .EXE and .?AT files to .EX_ and .?A_ So I imagine the trick is to fire up cmd.exe and run the various batch files in order from that prompt. I do the same thing with my setup, where batch 0xxxx are run first, then 1xxxx etc. If you make a change to something like 1xxxx , then the various later ones have to be run. Jolly good show, and another happy camper here!
  12. You won't see more than 4 GB of ram, but i believe there is a ramdrive that you can load into xms memory (ie > 4GB). You need to hack the install diskette to include the 48bit LBA addressing into it, but otherwise it would be fine. Check out this thread http://www.msfn.org/board/topic/75713-48-bit-lba-on-win2k-setup/ especially, my batch file for doing this.
  13. Boot to dos, and then run setup with parameters. You can tell it to read a setup.inf file from the c:\ drive or from a floppy. That's how i normally install it.
  14. Even though setup runs in the DOS console, it is still a windows app. In any case, it's looking for UXTHEME.DLL, which is not part of win2k. The win2k version of this might get around problems here. Compatibility mode just changes some answers that the OS provides the application, it does not add files that are not there.
  15. There are some things to note about UMBs on modern machines and Windows. 1. You should avoid using UMBs under Windows, since this slows it down somewhat. Have a look at UMBPCI on the web on this. 2. Modern machines use more UMBs then the average 486, so there's less for DOS. UMBPCI will find out what's available. I generally try to avoid WFW311, sticking with Win311. Still, i don't think there's a lot of changes.