dencorso

Here's something for you. I'll post about my detailed configuration next: How to restore the saved desktop layout at every logon. With desktop restore installed plain-vanilla, arrange the desktop to your satisfaction, then right-click on the desktop and select "Save Desktop", and this'll cause it to store what it calls "Default_Layout". Now copy the command line version of Desktop Restore, named "DesktopCmd.exe", to c:\windows/system32. Then right-click on the desktop, select "New", then "Shortcut" and give the wizard the following command-line: %windir%\system32\DesktopCmd.exe Restore /n Default_Layout /y And it'll create a shortcut named "DesktopCmd.exe" on the desktop. Rename it to "RestoreOrder", drag it and drop it onto the "Start" menu, then delete it from the desktop. Now, click on the "Start" button, locate "RestoreOrder", drag it onto programs, "Startup" folder. From now on, each time windows starts, DesktopCmd will run and restore the order you've saved, no matter whether it has been messed up or not. Just do not forget to "Save Desktop" each time you make a change in layout that you want to stick.

A good test would be getting a 5-pack, burning them, then checking them every half-year for corruption and posting about it. I just wonder whether there'll be any forums to post and drives capable of reading them, say, 100 years hence, when the test would be starting to get statistically relaiable...

grub4dos

That's the way to do it.

There's no such a thing as a dumb question. Here. It's in a sticky thread... Search before posting.

Welcome to MSFN!

@duffy98: I shall answer your questions shortly. Right now I've just done a major thread surgery, to keep things in their proper threads, and I have no time left to write you a proper reply. @everybody: Please let's continue the discussion about Icon desktop layout restoration here in this thread, OK? Thanks!

No, I do not know how to configure XP to create icons in line, instead of diagonally. And despite using XP for many years already, I've never noticed which is the default behaviour, since I rarely copy more than one file at a time to the desktop, in the rare occasions in which I do copy anything to the desktop. Sorry! I do, however, hope some other user will be able to solve your issue. ================ @everybody: Please do keep on-topic! This thread is *NOT* about restoring the desktop icon layout, and if that's what you want to discuss, please do go to Desktop Icon Order Keeps Changing instead, which is the correct thread for discussing it. Thanks in advance!

It's: powercfg -h -size <value> where, AFAIK, <value> specifies the desired hiberfile size in percentage of the total memory size. It cannot be smaller than 50. This command also enables automatically the hiberfile.

In answer to duffy98's question: yes, it's OK to quote other forums or provide links to other forums or both, as long as one is no pointing to or quoting anything that violates our rules. In other words, bphlpt's interpretation of the rules is correct. I have, however, edited somewhat duffy98's post just to show how to indicate clearly that something is a quote. I may have overdone it, so duffy98 may want to re-edit the post, and is, of course, free to do so. Now, as to using the NoSaveSettings as a general solution, I do think it's an overkill. When you set it, no seettings whatever, including windows sizes and positions, or any other tweak one may do, gets saved. To fight the icon layout haphazard changes, I still think the Midiox Desktop Restore is a more commensurate solution. That's just my 2¢, though.

There's KVR400X64C3A/1Gs galore at eBay, and amazon.com still has them, too. There really is no need at all to decomission your i-RAM.

Congratulations! It's a good board, and all you need as far as support goes is in its page at the ECS Site. I do, however suggest you add a fan to its Northbrige heatsink, and a passive heatsink to its Southbridge. Akasa has a chipset cooling kit (AK-VCX-01), which is perfect for this purpose, although it'll cost you more than you've paid for the mobo, and it has more parts than you need: a 28 x 28 x 8.75 mm heatsink for the 8237 and a 40 x 40 x 10 fan for the Northbridge heatsink are the only parts you'll need. I always add such complements to my KT-600 mobos, except those by SOYO, which have them already. As for the SATA connectors, they're SATA I, be sure to jumper any SATA II disks you decide to add to it, before installing them, or they won't work. More than that, it's a v.2.0! Those boards have just two slots for RAM, so they cannot take more than 2 GiB, and they don't come with the fan on the Northbridge and the heatsink on the Southbridge... any and all Dragon v.2.0 boards aren't a good idea.

Use, instead, midiox desktop restore... In many situations layout.dll fails to perform a correct layout restore, after it gets messed up. But I've never found one single system where midiox's files didn't work, up to now. I've never investigated in full this problem, but the author of the midiox desktop restore (Jamie O'Connell) published some notes about it on his site, for which I gave a link above. There is also a forum dedicated to it, there. And it's freeware! Get both the GUI version and the command-line version. Then sort the desktop and save the layout. If you use regshot just before and just after saving the layout, you'll find where in the registry it saves that info. Then create a .reg file from it. Create also a run entry to run the command-line version of desktop restore, and set it to restore your custom layout on startup. For the unattended you should merge to the registry those two regs, the one that has the custom layout and the one that runs desktop restore.

SOYO SY-KT600 DRAGON Ultra Platinum is a real good choice. It can use 2 GiB DDR RAM @ 400MHz or 3 GIB DDR RAM @ 333MHz, as do all boards based in VIA KT600. It's not an M chipset, though, so it has no onboard video included.

One possibility is that you might have to use double quotes around the path/filename containing spaces... Do give my modified version below a try and report. attrib.exe -h %windir%\shelli~1 del %windir%\shelli~1 attrib.exe -h %windir%\ttfcache del %windir%\ttfcache if not exist %windir%\inf\tweakui.inf del %windir%\system\tweakui.cpl RUNDLL32.EXE ADVPACK.DLL,DelNodeRunDLL32 %24%\"Program Files\Common Files\Microsoft Shared\Replman" RUNDLL32.EXE ADVPACK.DLL,DelNodeRunDLL32 %24%\"Program Files\Common Files\System\Comp"

You certainly are thinking of this.

v.2.96.5 of XXCOPY is the last ASCII version. Later versions are UNICODE, and while Unicows.DLL may enable one to use it, there's no telling which quircks may lurk in them. Test any later version *very* carefully to validate what it does well, before trusting it. For mission-critical tasks, like incremental backups, I do use the latest version while on XP, but on 9x/ME I don't trust anything above v.2.96.5, which is guaranteed (by Kan Yabumoto -- the author -- himself) to work. This snippet of info quoted below shows the telltale remark "Unicode support", which usually means "not anymore for 9x/ME".

Benvenuto al MSFN! [= Welcome to MSFN!] Although this is an English-only forum, occasional text in other languages may be used, provided it's duly translated, as I did above. I'm sure you'll enjoy it here, so, please, do feel at home.

Well, I've been using KT600 and KT400 based motherboards for a long time, already, and have not experienced any problems due to any chipset bugs, either. But now that pointertovoid mentioned it... way back when, there was talk about problems with older VIA chipsets... including the KM266. There're purported fixes for these purported issues by one George Breese, who seems to have been well known at that time, apparently because of those fixes. I've never used George's fixes, so I cannot say whether they were any good, but his homepage still exists. He seems to have been most active at the old www.viahardware.com forums, which also still exist, but now are located at sudhian (which just closed down, but still is available read-only, nobody knows for how long). Now, maybe some good spelunking around the oldest threads at sudhian can produce useful information, and if you decide to do it, do it now, while the sudhian forums still exist. Hope this leads somewhere, and in case it does, please do let us know. AFAIK, the VIA 4x1 4.38 (see this) should be enough, though, and George's fixes should not be necessary. Read also: Crash Test: Problems with VIA's KT133/KT133A.

Yes. I know well the Restart in MS-DOS Mode Issue... it is as you described. And I have a GeForce 2 MX 400 that showe that issue, as I described in the post I linked to. I use Win 98SE. To me, the Restart in MS-DOS Mode Issue clearly depends on the version of the nVidia Driver used and on the card used, but it must also be related to some specific hardware, probably the chipset, since it's a much less common issue than the Shutdown Issue. Most users never experienced that issue, or there would be more reports of it.

I may have found something useful, by searching WIDCOMM drivers, prompted by your suggestion. Here are some potential candidates to test. The XP WIDCOMM Bluetooth Stack can be made to accept almost any Bluetooth Radio by editing the .inf, in the same way as we do with NUSB on 9x/ME, so perhaps one or more of those 98 WIDCOMM drivers can be turned into a general solution...

Whitesnake - Guilty of Love

Secure Erase aka HDDEraseWeb is the fastest way to completely erase an HDD. It uses ATA native commands to do it, it's much faster than common wiping. After using it, however, you'll have to repartition and reformat from scratch.

On my rather old harware USB 3.0 can do that in 7 sec. On a razor-edge hardware, it can go down to about 3 sec. Using XP in both cases, of course... there're no drivers for USB 3.0 for Win 9x/ME, and it's unlikely there ever will be any.

May I suggest the Bluetooth stack as a worthy target? There's a little more info on it here.