jumper

> Can you solution work where the venue doesn't have WiFi? Would the HDMI wireless receivers (to plug into the projector) work in this solution? Ad-hoc wifi might work, or use you phone to create a private hotspot. Roku or Firestick could act as receiver. > ...the only common denomination being an HDMI port/cable to plug [into] my laptop ... placed near me instead of near the HDMI port/cable. An HDMI extension cable? > And just to add - the receiver/transmitter packages are not a via solution due to the transmitters power supply requirement (normally 2A) which my laptop can not provide. AC power adapter or powerbank. You could also do the PP presentation on a Chromebook or even your phone and cast it to a Chromecast. Or iPhone to Roku!

Correct. COPYCMD is only for specifying file overwrite parameters /Y and /?. It is also used by XCOPY and MOVE, not just COPY.

You have a cpu-incompatible version of ucrtbase.dll on your system.

So you want to mirror your screen--VLC can do that via DNLA by selecting screen:// as the streaming source. DLNA is the only wifi-casting technology supported by XP. VLC can stretch it to its limits. Otherwise you will need a hardware-only solution such as wireless HDMI (transmitter and receiver pair). You can also record (or covert) your PowerPoint to a movie and stream that with VLC, pausing as needed during the live presentation.

Use DLNA and VLC for media; screen:// as source to mirror.

The GPU is the chip on the card, not the video card itself. Each video card is a bus-master device so each GPU can directly access main memory while running its own code, just like the CPU. Each display driver gets a slice of CPU time to refill the GPU instruction and data pipelines so it can keep running concurrent to other GPUs and the CPU. Later NT versions have the equivalent of drivers for each CPU/core/hyperthread built into the OS. Windows 9x and earlier do not so can only make use of one CPU core. ATI didn't fully overcome the one-core CPU bottleneck--the display drivers still use it. But by creating powerful multiple GPU/core subsystems with lots of private, higher performance RAM, they were able to off-load most of the complex graphics rendering from the single, shared CPU.

Moving a folder tree on the same volume should retain creation and modification dates. Moving to another volume is a copy/delete operation and the OS will give all items new creation dates. This could be post-processed by modifying the directory entries with low-level calls. Otherwise the system date and time would need to be temporarily changed as each item is moved.

4.62 on 98 is the only combo I currently have. I recall having the same issue with 9 and 16 on 98se. I've downloaded some earlier versions (along with the source) and will test them on 98.

I get "File system error (1026)" with 4.62 on Win98. NT5+ might be needed for drag and drop to work in any version. I'll try the older versions.

The last updates don't solve his problem.

What versions have you tried? Maybe 3.13 or 4.20?

Dependency Walker is not for drivers, so things might not be all that grim.

So SSE2 is required. For SSE, modification is needed. How is that done? > This can be set under Preferences. Thanks!

Any minimum CPU requirements?

I'd prefer a "defuse" -- a "fix" should make it explode more often!

So it's good now for over a year. Then if the crash is at launch, open it the night before the five crash dates and leave it open. Or maybe set the system date back a day, launch, then correct the date?

Remove the filename to get to the download folder, then click the link. Create a new topic on how Let's Encrypt is relevant to the Chromium problem.

How did the PricelessWare testing go?

Downloaded three different ways, I always get a 37.4KB 150x150 PNG file.

For XP you also need an API extender. See reddit link for more details.

If the sponge thickness is the correct match for that HDD, there should be no pressure on the cable.

It's for NT 4.0 only. It has limited HDA support and might not work with your hardware, anyway. Test by installing NT4 and then Snap Audio.

Msdos.sys should work the same as in 9x. In [Options] try: BootGUI=1 Bootdelay=2 Bootmenu=1

No. VESA BIOS Extensions (VBE) graphics only support 2D. Any 3D must be done in software. "Notes: -This driver does NOT support 3D acceleration."

65025 = 255 * 255