Powermenu 1 38

1. Powermenu 1 38 Cm
2. 1.38 Inches
3. Powermenu 1 38 Sailboat
4. Powermenu 1 38 Sailboat

[Please note: To avoid further neglect, this page is now maintained by Gaby Chaudry (you may know her Windows 3.1 site).]

'PowerMenu' is a free utility which provides this essential feature which Microsoft has not implemented in Windows yet. It adds following 4 extra options in Windows control menu (the menu which appears when you right-click on windows titlebar or its taskbar button). PowerMenu.exe is located in a subfolder of 'C:Program Files (x86)' or sometimes in a subfolder of C:WindowsSystem32—mostly C:Program Files (x86)PowerMenu. The file size on Windows 10/8/7/XP is 57,344 bytes. The PowerMenu.exe file is not a Windows system file. It can change the behavior of other programs or manipulate other programs. Power Menu Burrito with steak, reduced fat sour cream, real cheddar cheese, guacamole, pico de gallo, avocado ranch sauce, and romaine lettuce. As part of a site I'm trying to design I have a div with the id 'powersettings' when clicked it toggles a div with the id 'powermenu' and toggles the class 'blur' on my 'content' div and 'tab a's.

Before we begin: What's Win32s anyway?

Win32s is an extension for 16-bit Windows (3.1x) that allows the execution of 32-bit programs originally written for 32-bit Windows versions, such as NT 3.x, 4.0 and Win 9x. But please do not assume that every 32-bit program will actually run on Win32s: originally it was only designed for compatibility with NT 3.x, and only a subset of the Win32 API is supported (that's why it's called Win32s)! By the way: 16 and 32 bit apps can exchange data over the clipboard and use OLE functions (which means that you can put an image that has been created in Paint Shop Pro 3.12 32-bit into your Winword 6.0 document and edit the image in PSP when necessary; this only works if PSP is registered as an OLE server though).

Download of Win32s

Win32s 1.30c can be downloaded here: ftp.microsoft.com/softlib/MSLFILES/PW1118.EXE
or - if this link doesn't work - here: ftp://gaby.de/pub/win3x/win32s/ole32s13.exe

It's about 2.5 MB in size and comes with a 32 bit Help program, which is very useful, as it is a functional equivalent of the Help program of Windows 95; it can even read Win95 help files. Also included is a little game called Freecell, mainly for test purposes. And last but not least, the latest OLE files (v2.03) come with Win32s as well - OLE functionality must come from somewhere ;).

What kind of program is more likely to run on Win32s?

Multi-platform software is more likely to work with Win32s, such as the image viewer XNView (freeware, more than 100 formats), the math software Maple V (until Rel. 4; Rel. 5: Single-user version only), the raytracer POV-Ray (until V. 3.02, Win32s support dropped for V. 3.1; freeware), and, as I've been told, Adobe Photoshop until V.4. And of course we mustn't forget the kind of programs Win32s was originally intended for: a host of Win NT 3.x software (well, 'host of software' may be a 'bit' exaggerated..;). Jixipix hand tint pro 1 0 12 0.

Why are there so many programs that don't run on Win32s?

There are a number of reasons. To summarize:

The programmers must address Win32s specific problems; for example, good memory management is necessary to prevent resource leakage. That means extra work, of course. Additionally Win32s needs program and DLL sections that can be omitted in Win9x/NT. Another reason is that all the newer development tools do not support Win32s anymore (the last MS Win32 SDK that ships with Win32s is from 1996, for example), and today's compilers' defaults are usually incompatible to Win32s as well.

Now the details:

• If a program uses Win9x specific functions of any kind, multi-threading, relies on fixed addresses (meaning that it lacks relocation tables) or simply uses Win32 functions that aren't implemented in Win32s, then it won't work. In case of lacking relocation tables Win32s simply doesn't understand the format of the executable (resulting in an 'Invalid format' message).
• The registry database is another problem, especially if the program's keys contain spaces (' ').
• Console mode apps can run if they're well-written (e.g. have relocation tables etc.), but there are no output possibilities, which means that one can't see what the program is telling the user, including help texts, unfortunately. Additionally, they must be started from Windows; unlike in Win9x, starting them directly from a DOS box doesn't work. Examples of working console mode apps are the Win32 console mode version of the web server Xitami 2.4d7 and the image converter NConvert which comes with the Win9x/NT version of XNView (which BTW, is identical to the 'Win 3.x' version, except for other language DLLs).

For further enlightenment I've cited from various posts from Paul Chitescu (hope he doesn't mind):

[comments in italic]

(Date: Wed, 30 Jun 1999 16:53:38 +0400
Forum: microsoft.public.win3x_wfw_dos)

Waves complete 2017 10 10 download free. Top reasons why a 32-bit applications won't run on Win32s :

• They use fixed address that are unavailable in Win32s
• The installer wants NT or 9x - but there are solutions ..
  [see his user page's software directory]
• Use multithreading (but 95% of them dont' really need MT)
• Use functions implemented in IE4 - 32bit
  [Active Desktop or the Windows Scripting Host, for example]
• Are linked to Win32 specific thunking code
• Are linked to Win9x specific DLL ordinals

As a general rule, well written applications have more chances to run on Win32s. I managed to run (up to a point) MS Word 95 and Excel 95 under Win32s - and those are heavy programs. Why such an application can run and a pityful applet that strips the Internet cache can't - answer yourself.

In the same message he wrote about his modified version of shell32.dll:

Many applications are not using purely Win32 API but also '9x specific ones. MS had to add some things to his NT 4 to keep such applications running (remember DirectX ?)

What I've done is a rewrite of the SHELL32.DLL that came with Win32s ersion 1.30C (that is, build 172). I disassembled that file and copied low-level thunking code as-is, except I stripped unreferenced setjmp() and longjmp() (Note: How did they link them there anyway ?).

• main enhancement : functions that return an OLE HRESULT now return correctly E_NOTIMPL. The MS version does SetLastError(E_NOTIMPL) but always return 0 so programs assume everything is OK and won't call GetLastError(). That leads to GPFs;
• changed exported ordinals to match Win95, not NT;
• possibility to dynamically load another DLL(s) to implement more functions. All documented entry points are patchable;
• added the Win95 icons ;-)

[Direct download link for his modified version of shell32.dll]

Powermenu 1 38 Cm

I've written a DLL that extends this version of SHELL32 by implementing Shell_NotifyIcon() (both A and W, I've found later that 9x implements only the ANSI version) and SHAppBarMessage(). When I have more time I will implement more SHxx functions.
[I'll ask him if he can put it in his user page's software directory]

In another post in the same newsgroup (dated Thu, 17 Feb 2000 12:29:45 +0200), he wrote the following about memory management in Win32s:

[Someone had encountered an Error 21/'Invalid Format' message from Win32s]

1.38 Inches

Unfortunately the VC++ 5 and 6 compilers default to not generate a .reloc section in applications so the .EXE can be loaded only at its fixed base address (default 0x400000) that is not available in Win32s.

There's no way around this error because of the different memory organization in Win32s where all programs share the memory in a single virtual machine. In a true Win32 environment each 32bit application gets its own virtual machine in which all the address space is free.

List of compatible apps

Legend:

• 'mp' means multi-platform software.
• Especially 'friendly' apps are marked ':)'.
• Programs that are also friendly, but which suffer from minor problems (difficult installation, resource eating or slight instabilities), are marked ':|'.
• Programs suffering from major instabilities (thus being only useful for experiments) are marked ':('. The third category is constituted by programs not intended for Win32s (as you may imagine).
• Smileys in brackets mean 'not sure'.
• Question marks stand for 'unknown'.
• The license types are COM (commercial [payware]), COM/DEMO (commercial, w/ demo version), FREE (freeware), SHR (shareware).

Note: Many thanks to Gaby Chaudry, who has added quite a few programs in the past :).

Win32s related downloads

I have some localized (=translated) Win32s 1.30c DLLs, but I'm not going to upload them, as they are quite large (German language files: approx. 607 KB zipped). If you'd like to have Danish, German, Spanish, Finnish, French, Italian, Dutch, Norwegian or Swedish DLLs and Winhlp32, just write to me and I will send them to you.

Windows NT 3.51 compatibility

Powermenu 1 38 Sailboat

One could call NT 3.51 'Win 3.1 on steroids', and there certainly is some truth to that. However, under the 3.1-ish hood it doesn't bear too much resemblance to plain Windows 3.1x - it's a 32 bit operating system which supports true preemptive multitasking, multithreading, SMP operation (NT Workstation: up to 2 CPUs, NT Server: up to 4 CPUs, NT Advanced Server: up to 8 CPUs), OpenGL acceleration (3D stuff), Unicode character sets/fonts and which runs much more stable than 'consumer-grade Windows' (partly due to virtually not having those nasty resource limits that drive you nuts in 3.1x).
Weaknesses are relatively few: No power management support, no support for plug and play (don't try removing PCMCIA cards when it runs!), only very limited (and thus virtually useless) DCI video acceleration. As you can see, it's not without a reason that the NT variants are called 'Workstation' and 'Server' - these names describe best where NT is able to play out its strengths (or the other way round: where its weaknesses don't matter much): office computers, graphic workstations (well, at least back then) and servers. Obviously it's not an ideal choice for multimedia or notebook computers. (This only changed with Windows NT 5.0 a.k.a. Windows 2000.)

Considering its 1995 release date (and 32 bit nature), it isn't all that amazing that Windows NT 3.51 is more demanding than plain 3.1x: 16 MB of RAM are the bare minimum, though even 24 megs will only allow operation of contemporary software (like Netscape 4.08) with lots of swapping; with 48 MB it's a lot better. Having become the proud owner of a dual Pentium 90 machine recently (Gigabyte GA-586DX rev. 3B, 48 (originally 24) megs of RAM from my old P75@90, a 540 meg hard disk, spare ELSA 2 meg PCI graphics card, 10 MBit PCI NIC), I decided to try NT 3.51 on it ('cuz it's 'the OS I've always wanted to check out').

Powermenu 1 38 Sailboat

It seems that this elderly OS has largely been abandoned, and quite a few newer apps will not run on it. (IMO this is a pity - it's a quite nice, stable OS.) The reasons for this are partly similar to those with Win32s:

• Missing NT4/Win95 specific functions (Kernel32/User32/GDI32)
• Missing HAL functions (most NT 4.0 drivers will not work, and getting ones for 3.51 is pretty much impossible with newer hardware - essentially the same problem as with Win 3.1x, but with a slightly larger possibility that 4.0 drivers might work)
• Dated versions of common dialog and common control DLLs
• No DirectX, of course (it doesn't work very well in NT 4.0 either, and needs kernel functions only available in NT 4.0 up)
• Missing OpenGL functions only implemented in NT 4.0 up
• Only Winsock 1.1 support, no Winsock 2.0, like in NT 4.0 / Win98 up (and optional in Win95)
• Different GUI behavior (mostly leads to cosmetic problems only, comparable to the same issues in Win 3.1x + Win32s)

So it's time for a compatibility list, don't you think?