Tweakin out a Win98se box

Status
Not open for further replies.
Here are a few quick, simple starters:<P>Under system properties, check your device manager and make sure your drives have DMA enabled. <P>Also, click on the Performance tab, select File System, and tell Windows your computer is a "Network Server." Then, click on the Floppy Disk tab, and uncheck the box that makes windows look for a new floppy drive on boot.<P>Then download Winboost 2000, and tweak like a villain. http://www.magellass.com <P>[Edit- Arg. I'm not talking about genetics. View image: /infopop/emoticons/icon_smile.gif ]<P>[This message has been edited by underthumb (edited December 16, 1999).]
 

Enigma990

Ars Scholae Palatinae
947
Subscriptor
Enough apps,<P>Lets get down and dirty with REGEDIT tweaks (aka Dangerous!)<BR>I'm always up for some danger with proformance tweakin!!<P>-E<P> View image: /infopop/emoticons\icon_wink.gif (keep in mind that i am not THAT familiar with the Reg)<P>Edit: Hey HippsterDoofus, that file PowerTweak is not correct, the zipped file is screwed up some how, could not lauch it after install. Bad file??<P>[This message has been edited by Enigma990 (edited December 17, 1999).]
 

Wesly

Ars Scholae Palatinae
1,068
Hipster:<P>Same thing happened to me when I tried to launch powertweak. Sometimes it just hangs, but sometimes gives the error:<P>Microsoft Visual C++ Runtime Library<BR>Program: G\powertweak\powert.exe<BR>abnormal program termination<P>As you can see, I did not install to the default location. Maybe I'll try that next. Something might be hardcoded as a subdirectory instead of the full path. Maybe I need a newer vbrun.dll?<P>Wesly
 
Dammit! You guys jinxed me!<BR>I d/l'ed and installed PowerTweak 2.0, but I didn't work (still a beta), so I uninstalled it and reinstalled 1.05b, and now I'm getting the same damn runtime error!<P>#%^&$#@(%#^!!!<P>I love that program, and I very badly want to get it working again. The guy who wrote it no longer supports older versions. Sonovabeech!!! What a prick! (Sorry, but I REALLY love that program!)<P>Anyway, how do you troubleshoot this kind of thing? I know it has to do with versions of .dll's in the /windows/system folder, but that's about all I know.<P>Arrrgh!!! Please help!<P>Edit: P.S.- I love that tweaker so damn much, I might be willing to reinstall Win98 if I have to, to get it running.<P>[This message has been edited by HipsterDoofus (edited December 21, 1999).]
 

Thorax

Well-known member
795
Lets kick it up a notch...shall we ?<P>Go into Device manager...open every device ..and I do mean every one.<P>Look in the driver file details for each and write down any driver file names you find that are in parenthesis like [vmm.vxd].<P>This part requires winzip 7.0 or higher.<P>Open the .cab files on your win98se cd...find those filenames and extract to C:\windows\system<P>Reboot and enjoy<P>P.S. the files in parenthesis are files that are needed but not found by windows...putting them manually into C:\windows\system will allow them to be used correctly by the device....this can be verified by the files no longer being in parenthesis after they are added to \system<P>[edit: added post script]<P>[This message has been edited by Thorax (edited December 20, 1999).]
 

Skippy

Ars Tribunus Angusticlavius
7,079
Thorax, thanks for the tip but here is a quicker cleaner way to get the files restored. start/run type msinfo32, go to the "tools" menu and select "system file checker" specify the filenames that you have found in parenthesis and point file checker at your win98 cd. It will extract the needed files and place them where they are supposed to be.
 
Wow Thorax! I had the following files missing:<BR>vdd.vxd<BR>vflatd.vxd<BR>configmg.vxd<BR>ntkern.vxd<BR>vcomm.vxd<BR>vmouse.vxd<BR>vdmad.vxd<BR>from modem, mouse vga card and even from system devices such as DMA controller and system board. <BR>How does this happen? Windows just forget to put some stuff in the suitcases when it moves to its new home (your HD)and then it just learns to live without it?
 
They are NOT "missing". They are parts of the file "VMM32.VXD" which Windows "builds" out of the individual *.vxd components. Since each computer is different, each computer's VMM32.VXD is different. Whether this "composite" VXD file is a good thing or not is a hotly debated topic. Many people claim to have increased their system stability after manually extracting each component of their VMM32.VXD, many more say there's no difference, and many more still say it decreased stability. I did it once, with no perceptible difference, but at the time I did not know what I was doing in general, so my machine was crashing all the time, regardless. Now, I <I>do</I> know what I am doing, and Windows never crashes, (certain apps do, once in a great while, but not Windows), and I have not done the "VXD trick", on my current installation.
 
Status
Not open for further replies.