The post Taming Windows 95/98/98SE/ME Out of Memory Errors appeared first on The Silicon Underground.

The post Why my ramdisk techniques don’t work with XP appeared first on The Silicon Underground.

The post The worm that’s not a worm appeared first on The Silicon Underground.

The post What can I say about Tuesday…? appeared first on The Silicon Underground.

Wiping. I needed a program yesterday to securely wipe out a hard drive. I was just going to low-level format it, but Western Digital's drive suite, whatever it's called, refused to do anything to the drive because it was returning an error code of 0207. The drive still worked, but according to my Web search, an 0207 means imminent failure. Hey, that's why I needed to low-level the drive--we got a replacement for it and had to send this one back, but the drive was in an executive's computer and probably had sensitive data on it.

Incidentally, if you're getting an 0207 and you're here because you want to know what to do about it, back up your data immediately and get it replaced under warranty. No, it's not practical to fix it. If it's out of warranty, I'm sorry. Sadly, it happens.

But I digress. How do you wipe the drive to ensure no one's reading your sensitive data? I found some DOS freeware to do it at my usual sources, but one of them wouldn't run under Win9x's DOS, and the drive is too big to be recognized under 6.22. Another one wouldn't handle drives bigger than 2 gig. Another one seemed to work, but seemed awfully fast.

Disk wiping isn't a terribly complicated thing, so maybe I should just write a program myself to do it. It's been forever since I programmed, and I do kind of enjoy doing that... once a year. Or every couple of years.

The post Secrets about hard drive recovery and wiping appeared first on The Silicon Underground.

Then I set out to compress my ramdisk. Disk compression makes sense when disk space is expensive, and RAM is comparatively expensive, and even if disk compression slows it down by 100%, compressed RAM is still many orders of magnitude faster than a metal disk. I couldn't get it working. I didn't say it was impossible, because I'll never write anything off as impossible, but I said I couldn't get it working. I figured that'd be the last I'd hear of it.

Then over the weekend, Tony Brewer, a reader of the Optimizing Windows, wrote in, quoted that paragraph verbatim and casually said, "It's most definitely possible." I was flabbergasted. Had he done it? I wrote back and asked if he'd done it and if he'd be willing to share the secret.

Indeed he had, and he was kind enough to share the secret. It turns out I was very, very close to getting it working. But close is only good enough in nuclear war, not computers.

Here's what he had to say:

Dave,

There is an elegant and simple method for running Win9x on a compressed RAM disk. Assuming that Win9x is already installed on C: and using the same drive letters as in Chapter 11 of your book:

Run DriveSpace in Windows to create an empty compressed drive E: of the desired size using free space on C:, re-boot, then install Win9x to E:windows (with the swap file on C:). Edit c:\msdos.sys, c:\config.sys and c:\autoexec.bat as follows:

c:msdos.sys
------------------
[Paths]
WinDir=e:\windows
WinBootDir=e:\windows
HostWinBootDrv=c
...

c:\config.sys
-----------------
device=c:\windows\himem.sys
device=c:\windows\emm386.exe    ;or use umbpci.sys
dos=high,umb
devicehigh=c:\windows\ifshlp.sys
devicehigh=c:\windows\setver.exe
...

c:\autoexec.bat
---------------------
...
path=e:\windows;e:\windows\command;e:\windows\system
set temp=c:\ temp
set tmp=c:\temp
....

After re-booting, Win9x should run on the compressed drive E:, hosted by physical disk C:. To have a compressed RAM disk, the host must be an uncompressed RAM disk, D: for example. In c:d??space.ini (c:dblspace.ini or c:drvspace.ini, probably the former), change the ActivateDrive setting to read:

ActivateDrive=E,D1

This tells the DriveSpace driver to mount the compressed volume file (CVF) d??space.001 as drive E: with host drive D:. (Mounting is not automatic as it was with host drive C:, because RAM disk D: does not exist when io.sys loads the DriveSpace driver, dblspace.bin or drvspace.bin.)

Edit c:\autoexec.bat so that it contains the following:

...
path=c:\windows;c:\windows\command;c:\windows\system
REM Create RAM disk
xmsdsk {desired size of RAM disk in kilobytes} d: /t /y
REM Copy CVF to RAM disk
attrib c:\drvspace.001 -s -h -r
copy c:\drvspace.001 d:\
attrib c:\drvspace.001 +s +h +r
attrib d:\drvspace.001 +s +h +r
REM Mount CVF using scandisk /mount
scandisk /mount d:\drvspace.001
REM E: is now compressed RAM disk
path=e:\windows;e:\windows\command;e:\windows\system
set temp=c:\temp
set tmp=c:\temp
...

After re-booting, Win9x should run on the compressed RAM disk! :o)

(On a networked PC, there is no need for a hard disk as the CVF can be copied from a server. Diskless Win9x using a compressed RAM disk works very well.)

The above method is an adaptation of one by Andre Moreira. http://www.dei.isep.ipp.pt/~andre/extern/nc98.htm

Regards,

Tony Brewer
tonybrewer@bigDELETEfoot.com

With some thought, I may be able to simplify it a little, but not by much. The obvious simplification would be to use the free-for-private-use xxcopy to copy drvspace.001 in a single step, saving all those attrib lines in autoexec.bat.

This shows a lot of promise. Memory's so cheap right now that it's feasible to get 384 megs, leave yourself with 64 or even 128 megs of working memory, and still have a decent-sized ramdisk. Windows 95 will install to as little as 17 MB, if you know the secrets. Windows 98 is considerably larger but it's still possible to stuff Win98 and a couple of apps into a compressed 256 MB disk, and it's super fast. Even with disk compression, access to a compressed ramdrive is nearly instant. I did get compressed ramdrives working inside Windows (I just couldn't boot from them) and even on my Pentium-90 a compressed ramdisk was fast. So if you want maximum speed, this is the way. And I'm wondering what this would do for a laptop's battery life...

I'm really eager to give this a test drive.

The post The search for the compressed ramdisk is over! appeared first on The Silicon Underground.

Last night, I sent myself hurtling 120 miles at 75 MPH to Columbia, Mo. My mom lives there, and my alma mater, the University of Missouri, is also there. Today, after morning services, I'm headed another 120 miles to Kansas City, where most of my mom's family lives. I don't get back there very often, so I'm looking forward to it.

I've got some stuff to write, but I'll be late for services if I do, so it'll have to wait.
~~~~~~~~~~
From: "Lawrence Kim" <lykim@nospam.telusplanet.net>
Subject: A loyal reader w/a technical question

Dear Dave: I have a few questions, well, maybe just one, related to your book.  When you do a clean install of W98SE on a partitioned drive, if you wipe C: (where W98 is), how do you get the other programs on the other drives to run again?  Especially if you've wiped all the .dll files and other important stuff?  Secondly, what's a good and fast way not to have to reload all the programs again if you wipe & reinstall W98?  If I used Drive Image 4.0 or a tool like that (or maybe even Norton Ghost), how do you copy images of your drive back onto your computer?  Lastly, what's the best way to optimize your ADSL/highspeed Internet connection?  I've been using this program called NetSuperSonic which is supposed to adjust certain registry settings in Windows to optimize it for broadband use.  It seems to work pretty good, but I was wondering if you would have some other suggestions.  That's pretty much everything.  Oh yeah, are you going to come out with a new, updated book?  I don't know, just thought that I would ask. That's for writing the book; it's been extremely helpful.

Cheers.

~~~~~

I think that's actually more than one question, but that's ok of course.

The idea of a clean install is to start over, which of course means reinstalling everything. Reinstalling everything takes time, of course, but the benefit is that you're rid of all those old, no-longer-in-use DLLs and other leftovers that hang around after you uninstall programs. You've also got fresh copies of everything and a brand-new registry, which is good because registries get corrupt and so can DLLs and even programs. The result is a faster, more stable system.

But if you've lost the installation files for some of your programs, you've got a problem. You can use CleanSweep or Uninstaller to package up the program, DLLs, and its registry entries for re-installation, but be sure to test the package on another PC before you wipe, because these don't always work.

Ghost or Drive Image aren't a clean install per se, because they preserve everything. Generally the way I save and restore images is to a network drive, or in the case of a standalone PC, to an extra partition or, better yet, a second hard drive. You can also span an image to multiple Zip, Jaz, or Orb disks but that's slower and more cumbersome. These programs are absolutely invaluable for disaster recovery, but as optimization tools in their own right, their benefit is very limited.

If NetSupersonic checks your MTU and adjusts it properly (many of those utilities don't), that's a great start. You can measure your speed by going to http://www.pcpitstop.com/internetcenter.asp, and they have some suggestions on the site for fixing sub-optimal perfomance. Ad-blocking software will speed you up as much as anything else you can do, and FastNet99 (mentioned in the book) is also useful by reducing the number of DNS lookups you have to do (I accomplished the same thing by connecting my DSL modem to a Linux box running its own DNS, which I then used to share my DSL out to my Windows PCs).

As for an updated book, I imagine not doing one would probably kill me. But publishers are understandably hesitant to do one right now, since no one seems to know what Microsoft will do next. Is Windows Me really the end? Is Windows 2000's successor really going to be suitable for home use? When will Microsoft manage to deliver another OS? No publisher wants to invest tens of thousands of dollars in producing a book only to find out they guessed wrong. Once there are answers to those questions, it'll be time to write a new book. In the meantime, I'm writing magazine articles (there's very little new in the article at www.computershopper.co.uk this month; there are a couple of new tricks in the article for February, and the article for March is almost entirely new stuff) and posting new tricks to my own site as I find them or think of them. So the answer to your question is, "probably," but I can't give you any kind of time frame.

Hopefully that answers your questions. If not, feel free to write back.

~~~~~~~~~~

From: "Lawrence Kim" <lykim@nospam.telusplanet.net>
Subject: Drive Image Pt. 2

The post 12/24/2000 appeared first on The Silicon Underground.

Which reminds me, I really do need to get an OS/2 box running again, and get serious about BeOS while I'm at it...

Windows Me can't handle more than a half-gig of RAM. This also from The Reg. Story here. The vcache workaround is legit; no one has ever demonstrated to me the benefit of using more than 4 megs for a Win9x disk cache anyway.

The post Running something other than Windows is theft appeared first on The Silicon Underground.

There's the possibility that another publisher who's strong in Windows NT/Windows 2000, such as Sybex, might be interested. I haven't talked to anyone there about it yet. But believe me, I've thought about the possibility of such a book.

I tried to write Optimizing Windows in such a way that someone who knew Windows 9x and another OS would then be able to apply the principles to both OSes, even though the specifics would only apply to 9x.

In the meantime, the best suggestion I can come up with is to take yesterday's post , print it, then paste it to an otherwise underutilized page (such as the last page of the preface, which is totally blank). While it doesn't go into great detail, that message could well form the basis of a chapter in an NT/2000 follow-on. I'd say at least half of chapter 2 in Optimizing Windows (particularly the user interface stuff) applies to NT and 2000 as well.

Laptop troubleshooting. I had a laptop the other day that seemed to launch programs and move the mouse pointer around at will. I'd never seen anything like it before. We were perplexed about it for a couple of hours (it was a deployed user in California, so it wasn't like I could just tool over to his desk and start trying stuff). On a hunch, he unplugged everything and powered up the bare laptop. It worked fine. He started adding components one at a time, and when he got to the mouse, the problem reappeared.

Constant travel and frequent plugging and unplugging certainly could be hard on the mouse cable, so I can see where this might be a common problem for road warriors (I'd say 90 percent of my support experience is desktop PCs). So, if you're getting unexplainable behavior from a PC, especially a laptop, try a different mouse -- and a different external keyboard too, while you're at it -- and see if that makes the problem go away.

The post An Optimizing Windows followup? appeared first on The Silicon Underground.

The post Mac “superiority” and cheap PC hardware sources appeared first on The Silicon Underground.