dencorso

On a quite superficial inspection, I'd say I guess it *is* safe. In fact, the older IFSHLP.SYS is bigger (4548 bytes) and has more functionality than the later one (3708 bytes), and almost all the code in the later one is contained in slightly modified form in the older one, which also has more code, and hence, more functionality. Yet, a closer analysys should be done to ensure no patching is needed. But I think it's safe enough for you to test the older one in your Wfw 3.11, although that's just my first impression.

No, there's no reason to prefer XMSDSK. Since the CENATEK RD works OK for you, you should stick to it and move on. This means you've reached the definitive setup for the dino, doesn't it? If so, congratulations!

Well, that's good news! It means Windows is crashing due to exhaustion of the System Arena. For more info about it, read this post and those that follow it. On the other hand, were it DOS to crash instead of Windows, I wouldn't have the faintest idea of what the problem might be! So, let's troubleshoot it radically: 1) Set, in both system.ini and system.cb, MaxFileCache=114688 ; 112 MiB 2) Reduce the XMSDSK to 64 MiB. Try again and let's see whst happens after the WIN command.

Hi, Tihiy! It's good to have you around! And thanks for the sources, this ensures all the brainwork invoved in RP will be preserved. You do rock!

You said it crashes DOS. I doubt it. I think it crashes Windows. Let's see who's right. Set BootGUI=0 and Logo=0 in MSDOS.SYS, and try to boot substituting your current config.sys by the one attached. If you get to the DOS prompt without a crash, do a DIR command to make sure dos is working, then do a WIN command, for Windows to load. If it crashes only after the WIN command, pay attention to any message that it may flash and report it, or tell us there's no message at all. CONFIG.zip

Zip and attach config.sys and autoexec.bat. Let's pore over them and see what we find, OK?

What about Mosaic? Now, seriously: Pale Moon.

Forget HIMEMX.EXE. You don't need it at all, with 768 MiB RAM. Use MS HIMEM.SYS instead. But you do need to add both to system.ini and system.cb a [VCache] section having a single setting: MaxFileCache=114688 ; 112 MiB Then I think your XMSDSK will load OK. Let me know how it goes. PS: Loved your cooling solution!

Of course it has! But since you're at it, one of your wonderful batches to automate fully the operations descrbed in post #30 by fdv, incorporating your idea of using Tasklist, would be really handy, if you can find time for creating it...

Congratulations! BTW, since you now can connect pendrives at USB 2.0 speed, this is a great moment for acquiring a full-disk image as a backup, so that you'll never again need to install from scratch.

Awesome, joakim! A strike of genius! You do rock!

Try installing karyonix's DiskMod on 7 x64, and you'll be stuck with /TESTSIGNING for good. Whenever you decide to use any unusual, (but perfectly legitimate) driver, like the one I just mentioned, you'll have a motive to want to get rid (preferably reversibly) of digsig checking. That's why.

That's the best way of doing it. The oldest one is: at xx:xx /interactive %sysdir%\cmd.exe, where xx:xx is, say, one minute hence. This I bet doesn't work on Win 7, especially the x64 version, but I may be wrong. We're after getting total control of the system, for the rare occasions on which that's handy, IMHO.

Do the same methods that worked on XP succeed in making you the System user (= NT AUTHORITY\SYSTEM)?

Great idea!

You rock, GrofLuigi! I had utterly forgotten all about natsumerio's work (of course I'm growing old, but it seems my memory is failing me, too, sometimes ). While I'm not even near jaclaz's class, in what regards remembering things and locating related info, I'm usually not that absent-minded. I see I must do some mnemonic gymnastics right away, to shake off the rust from my brain!!! Of course natsumerio's approach is with a war-axe, not a scalpel, so things are bound to get nasty. But, then again, it sure is yet another starting point to consider, and interesting info in itself.

Since you decided to reinstall, you have nothing to lose in trying the following before going ahead with the reinstallation. So, please, do try rebooting and letting windows start (as far as it manages to) then shutting it down (unless it hangs/freezes, when a reset is needed) two or three times in a row. The system may manage to fix itself enough for us to go on. If not, then reinstall without ACPI, and give it the manufacturer's drivers and VIA's USB drivers, but do not install NUSB for the moment. BTW, it is Setup /p i not Setup /c i

Sure. Well, sorry! My keyboard froze and I had to reboot. It seems my latest edit before that to my post #25 never really made it to the forum. So... Please, do re-read my post #25 above, for now I've added the BIOS settings I intended to have changed. My aim is to move from ACPI to APM. Sorry again, folks! @TELVM: hexadecimal 2 = decimal 2 so you may choose either. But I should have said so, earlier. Then again, thanks to my keyboard, I didn't get the chance to before. Sorry!

submix8c certainly has a point there. But, on a machine that has problematic USB 1.0 onboard controller, the ACPI is usually even worse and sends people on wild-goose chases. So let's do away with both. Inside windows, open regedit and navigate to HKLM\Software\Microsoft\Windows\CurrentVersion\Detect, and then add as a new dword value: ACPIOption=2. Close regedit and shut down the machine. Turn it on again, and go into BIOS, and change all of the followng settngs as indcated: ==== Anti-Virus Protection: Disabled ==== Memory Hole at 15M-16M: Disabled ==== ACPI Function: Disabled PM Control by APM: Yes ==== PNP OS Installed: No Resources Controlled By: Manual Reset Configuration Data: Enabled (it'll disable itself after ONE reboot) Assign IRQ for USB: Disabled ==== Let windows boot into safe mode and remove all USB-related items, then reboot normally and let windos redetect them all. Let us know the outcome. Good luck!

Any pendrive or just a specific one? But even befor I read your reply, do the following, please: 1) Create an arbitrary folder, and name it, say, "seguro", it could be C:\SEGURO, for instance. 2) Go to C:\WINDOWS\SYSTEM32\DRIVERS, find USBHUB20.SYS, and copy it to C:\SEGURO. 3) Install NUSB 3.3 Spanish. Another thing, did you disable the onboard USB controller in the BIOS? If you're using PS/2 mouse and keyboard, that should be the safe thing to do.

We don't really know that. Younger people prefer blogs (which then disappear in the night) and IM over forums, and don't really love documenting what they did to get the job done. So, it may have been done already but never documented anywhere. But I think GrofLuigi has a point, too: but my take is it may not be necessary to dethrone TI, provided everybody in the Admin group has equally full rights... democratizing TI's rights surely is the kind of subversion that fits my tastes. Then again, blowing WRP to smithereens can maybe be simpler to accomplish...

Scorpions - Humanity

Biquini Cavadão - Chove Chuva (rock version, of course!) http://www.youtube.com/watch?v=GT_txmMbQcg

It's a venerable VIA 6202! Whatever the maker/brand of the board, provided it's not dead/broken, VIA's own reference drives will recognize it! The multilanguage pack is downloadable from the official link (viaarena).