MDGx

edit 7-23-2005 Petr: I would like to suggest to add these newer files to your next 98FE SP release: Petr suggested we should try Win2000 Post-SP4 Q886765 OLE2 DLLs. I have tried them with both 98SE + 98FE and so far they work ok: ASYCFILT.DLL build 2.40.4526 OLEAUT32.DLL build 2.40.4526 = does NOT work, must use older OLEAUT32.DLL 2.40.4522 from Win2000 SP4 OLEPRO32.DLL build 5.0.4526 STDOLE2.TLB build 2.40.4526 Source: Microsoft Windows 2000 Memory Leak ASYCFILT.DLL, OLEAUT32.DLL, OLEPRO32.DLL + STDOLE2.TLB Fix: http://support.microsoft.com/?id=886765 Direct download [658 KB, English]: http://www.mdgx.com/files/Q886765.EXE posted here: http://www.mdgx.com/w2ktoy.htm#W2K If you wish to install them yourself directly without extracting them manually, please d/l this unofficial fix: Unofficial OLE Update build 2.40.4526 for Windows 9x/NT4/ME [446 KB, English]: http://www.mdgx.com/files/OLEUP.EXE posted here: http://www.mdgx.com/add.htm#OLE ________________________________________ I have also tried these 2 newer files from VB6 Post-SP6 Update with both 98SE + 98FE and so far they work ok: COMCTL32.OCX build 6.00.8106 MSCOMCTL.OCX build 6.01.9786 Source: Visual Basic 6.0 (VB6) Post-SP6 COMCTL32.OCX build 6.00.8106 + MSCOMCTL.OCX build 6.01.9786 Common Controls Update for Windows 98/NT4/2000/ME/XP/2003: http://support.microsoft.com/?id=896559 Direct download [914 KB, English]: http://download.microsoft.com/download/3/a...6559-v1-ENU.exe ________________________________________ I have also tried these 2 newer files from Win2000 Post-SP4 Update Rollup 1 with both 98SE + 98FE and so far they work ok: DHTMLED.OCX build 6.01.9232 WRITE32.WPC build 2004.11.7 Source: Microsoft Windows 2000 SP4 Update Rollup 1 (UR1): http://support.microsoft.com/?id=891861 Direct download [31.1 MB, English]: http://download.microsoft.com/download/8/4...861-x86-ENU.EXE ________________________________________ I got this email from the person who created the unofficial 98FE/98SE KRNL386.EXE patch: Unofficial Windows 98/98 SE KRNL386.EXE build 4.10.1999 Fix [172 KB, English]: http://www.mdgx.com/files/98KRNLUP.EXE posted here: http://www.mdgx.com/web.htm#98SE IMO sounds like a good idea to add patched KRNL386.EXE to your next 98FE SP release.Hope this helps.

Per the advice from the person who created this voltrack.vxd patch, I have reverted back to voltrack.vxd build 4.10.1999, so users would not be mislead in thinking this newer [4.10.2000 unofficial] build includes also the [official] Japanese edition patch from Q234697: Hope this helps.

Petr, This is what I found on Compatibility Flags: MS TechNet: http://www.microsoft.com/technet/prodtechn...E12E3D1F8B.mspx WinGuides: http://www.winguides.com/registry/display.php/1188/ Hope this helps.

May I also have a copy, please?U know my email. Thanks in advance.

Petr, Actually all these 3 files are identical [i didn't list the 3rd here because doesn't apply to 98/ME]: - MS IE 6.0 SP1 Patch for Windows 98/98 SE/2000 SP3/2000 SP4/ME/XP SP1 [106 KB]: http://download.microsoft.com/download/9/0...235-x86-ENU.exe - MS IE 5.5 SP2 Patch for Windows ME [106 KB]: http://download.microsoft.com/download/3/1...235-x86-ENU.exe - MS IE 5.01 SP3/5.01 SP4 Patch for Windows 2000 SP3/2000 SP4 [106 KB]: http://download.microsoft.com/download/f/1...235-x86-ENU.exe

R u loading SMARTDRV from config.sys or autoexec.bat on that 98SE boot CD?Because that CD [besides spinning way slower than a HD] loads probably only a minimal Windows GUI, and in that case probably doesn't have 32-bit disk/file cache enabled, so it runs in slower "MS-DOS compatibility mode". The only fix for that is smartdrv. Example [for single HD/partition = C]: - autoexec [no need to load it with LH, cuz smartdrv loads itself in UMA if it detects an UMA manager already resident in memory]: SMARTDRV 12288 C+ /N /Q -config: INSTALLHIGH=SMARTDRV.EXE 12288 C+ /N /Q This gives Windows 12 MB of disk cache, but works only in "MS-DOS compatibilty mode". FYI: to load smartdrv "high" in config.sys [a.k.a. in the Upper Memory Area (UMA)], u need an UMA manager like UMBPCI, QEMM386, RM386, 386MAX or MS EMM386.EXE in config.sys. UMBPCI [the best + it's free] requires compatible mobo chipset to work properly: http://www.mdgx.com/umb.htm complete list of chipsets that work with UMBPCI: http://www.mdgx.com/umb.htm#REQ chipsets with problems: http://www.mdgx.com/umb.htm#CHI You can find more details on how to do this [and more DOS tweaks to maximize performance] in MEMORY.TXT, part of W95-11D.EXE [1.15 MB]: http://www.mdgx.com/95.htm Have fun.

What does that setting actually do? Ive installed win98 and win2k with that option set to yes and no, and I didnt notice any difference (not that I was examining it with a magnifying glass or anything though).1. Never used NVidia mobo chipsets, but 2 things come to mind:- hex older nforce3 drivers [if NVidia posted hardware specs +/- source code] or - install nforce4 drivers from within WinXP, then reboot in 98SE and mod the INF(s) to force them to install on 98SE. Like I said, never used NVidia mobo chipsets, so this is just a theory. 2. PnP OS enabled/disabled in BIOS used to be heavily used on [some] 440BX Intel chipset based mobos to fool 9x/ME/2000 into re-shuffling the hardware IRQs [and other resources] independent of BIOS settings. If enabled, this option used to either lock up the PC or the OS was unable to use IRQ steering properly, which usually resulted in "down-grading" to "MS-DOS compatibility mode". Hope this helps.

Salut. Cum este vremea la Craiova? English: Hello. How is the weather in Craiova?

Sorry for the delay, but all MS05-037 links are now posted here: http://www.mdgx.com/ietoy.htm#JPX and here: http://www.msfn.org/board/?showtopic=46581 including the manual REG fix, which doesn't require any downloads. FYI: MS05-037 Security Vulnerability Fix Bulletin was formerly published by MS as Advisory Bulletin 903144: http://www.microsoft.com/technet/security/...ory/903144.mspx Hope this helps.

Make sure [if u haven't already] you install current NForce drivers for your OS and then reboot. NVidia Drivers: http://www.nvidia.com/content/drivers/drivers.asp Make sure your mobo BIOS setup has the "PnP aware/compatible/enabled OS" option or similar disabled. Make sure Device Manager has the "IRQ steering" [Control Panel -> System -> Device manager -> System devices -> PCI bus -> IRQ Steering tab] option enabled. If using any USB peripherals make sure "Use IRQ for USB/USB Uses IRQ xx" or similar mobo BIOS setup option is enabled. More USB troubleshooting tips: http://www.mdgx.com/98-5.htm#FWUE Use a detection tool, like PCI List [freeware]: http://www.entechtaiwan.com/files/pcilist.exe to learn [if u don't know already] who is the manufacturer of your mobo built-in (E)IDE/(U)ATA hard disk controller, and then install appropriate chipset drivers. If your HD(s) is/are connected to other [3rd party/proprietary/custom/SCSI/RAID/SATA] HD controller, make sure you install current drivers from manufacturer/vendor web/ftp site. I have no experience using SATA controllers/drives with 98SE/ME OS, but I've read about frequent problems, because SATA drivers are developed mostly for 2000/XP/2003/Longhorn, because it is a newer technology, and at the time of its release MS stopped supporting 9x/ME OSes. HD controller drivers links: http://www.mdgx.com/drv.htm#DRV Try to disable ACPI/APM/power saving/standby/etc features from your mobo BIOS. Power saving troubleshooting tips: http://www.mdgx.com/newtip15.htm#MYP Make sure you install 98SE SP 2.0.1 [if u haven't already]: http://exuberant.ms11.net/98sesp.html and forum here: http://www.msfn.org/board/?showtopic=46399 to fix some hardware detection bugs. You may also want to consider installing Native USB Drivers: http://www.msfn.org/board/?showtopic=43605 to upgrade USB support to WinME level. So does 98SE2ME: http://www.msfn.org/board/?showtopic=46349 which installs most USB + WDM drivers from WinME setup CD. If u load any drivers from CONFIG.SYS or AUTOEXEC.BAT, please take a look at this tip: http://www.mdgx.com/newtip6.htm#IOSINI to learn how to avoid "MS-DOS compatibility mode" errors by editing your IOS.INI. Hope this helps.

Sorry, I didn't know it froze your computer for over 20 minutes. Bummer. Never froze on my PC, so I couldn't reproduce that. ;(But I'm glad it works properly now. MAPI32.DLL is responsible for e-mail interface in all Microsoft apps [Outlook, Outlook Express, Exchange etc] as far as I know. MAPI = Messaging Application Programming Interface More info: http://www.outlookcode.com/d/mapi.htm Even more info: http://www.darkweb.com/~beng/exchange/mdevfaq.htm The newest build that supports 9x/ME is the 1 from WinME setup CD as far as I'm aware. My guess would be that the programs that replace the MS file with their own, probably install a fake API/stub, therefore the difference in size. I have no idea why they do that. You may want to email them [Ahead Nero for example] and ask. Hope this helps.

Very glad it works properly on your computer now. How I do it: with a lot of patience, experimenting + [never enough] time set aside for testing. Enjoy.

7-Zip [7za.exe] is designed to work only in Win32 GUI mode, even if it is a ["console" as it is also called in NTx] command line tool. Does not have a real DOS mode module. It's pure 32-bit.If u would like to have real DOS mode support for the 7Z format, u could email the author and ask if he plans developing such feature: http://www.7-zip.org/support.html Bummer, I guess I won't replace xclone with 7za.exe in 98SE2ME after all. FYI about the 2 WDMAUD.* files from ME: I've also installed them on a friend's PC who has a CL SB Live! 5.1 Gamer PCI audio card, and works great so far. Hope this helps.

Amen, brother

I'm sure they'll show up soon... But I'm not worried about them, I'm also using XP OEM since 1 month before the retail edition was out [september 25 2001], but I still prefer 98SE, cuz it's more fun to tweak. B)

Thanks for the info. I'll look into the doslfnbk license. PK(UN)ZIP sucks big time: it is LFN compatible only in Win9x/ME but not in NTx, and like u said, it doesn't have a clue about LFN/SFN aliases. I prefer 7-zip command line [7ZA.EXE]: http://www.7-zip.org/ because it is 100% free [GNU GPL license], and creates much smaller ZIPs than PKzip, and besides, 7-zip is LFN compatible with all 9x/NTx releases. I haven't checked 7-zip for accuracy on keeping LFN/SFN aliases, though. If u have the time and test 7-zip, please let me know. About the wdmaud.* files from ME: I haven't received any error reports, but u never know, it could depend on audio hardware. [?] I am using both these files since 7-1-2005 with my CL Audigy2 Platinum PCI sound card, and haven't experienced any errors so far. But as usual, these 2 files are tied into other *.SYS [WDM style] drivers 98SE2ME replaces with ME files into %windir%\system32\drivers , so they wouldn't work just by themselves. I can only hope for the better.

All the boot IMG/ISO downloads u can shake a stick at: http://www.mdgx.com/drv.htm#CDR Hope this helps.

Everything u need to create unattended 98/98SE/ME setup CDs: http://www.mdgx.com/add.htm#DEV Hope this helps.

There are actually 2 different issues to consider here:1. LFN + SFN naming convention for file + directory names built into every file + directory entry = those are strictly kept, they are "hardwired" into the file/dir entry header, cannot be changed unless file/dir is renamed or deleted [but if recently deleted, then u have the problem of wrongly assigned "aliases" - see 2. below]. 2. SFN "alias" created by OS or file/dir manipulation tools to corespond to LFN of same file/dir = relative, not hardwired, changes every time, depending on what other SFNs already exist [and which cannot be overwritten, unless u use a dedicated LFN tool like DOSLFNBK or XXCOPY] in same directory [for file names] or on same disk/partition [for directory names]. LFN/SFN convention [1. above] must be kept at all times for HD integrity. SFN alias is the problem you are reffering to: wrong ~1 or ~2 etc SFN names for LFN files/folders, no matter if OS settings [registry, INI, SYS, CFG, BAT etc files] are different, because there is no OS feedback check facility to preserve them properly. And exactly as you said [i haven't done this kind of experimenting], doslfnbk + xxcopy are probably the only ones that properly backup/restore/copy aliases, by reading correct SFNs. Om my PC I have eliminated all LFNs that could cause such problems, because I've noticed this issue early on, way back in the Win95 days. So I renamed all LFN folders to SFNs [and of course, modifed all system/setup/boot/etc files, including the registry accordingly]: - C:\Program Files to C:\PROGRAMS - C:\Program Files\Windows Media Player to C:\PROGRAMS\WMP - C:\Program Files\Internet Explorer to C:\PROGRAMS\MSIE - C:\Program Files\Common Files to C:\PROGRAMS\COMMONS - C:\Program Files\Common Files\Microsoft Shared to C:\PROGRAMS\COMMONS\MSSHARED - %windir%\Downloaded Program Files to C:\PROGRAMS\DLPROGS - %windir%\All Users to C:\PROGRAMS\ALLUSERS ... etc, u get the idea. Also, deleted C:\Program Files\Accessories and few others that I don't care for anyway. So in case I backup the entire OS, I have no folders with LFNs to worry about, only a few LFN files, and because those have unique names, the probability of assigning wrong SFN aliases is extremely small [never ran into problems so far]. I also recommend to everybody to save their entire registry as a REG file, replace all "C:\Progra~1" instances with the proper "C:\Program Files" string [and eventually all other similar LFN folders which are wrongly represented inside the registry as FNAME~1 or FNAME~2 etc], and then rebuild the registry from native DOS mode [example : regedit/c c:\reg\reg.reg]. It takes a lot of time to do all this, but it's a 1 time thing, and in the long run it saved me from all related troubles. This is [as I was telling VWIMaster in this post: http://www.msfn.org/board/?showtopic=49538...ndpost&p=350569 ] 1 of the reasons I never reformat my HDs/reinstall my OSes every time I bump into a bug. I find more interesting to solve a bug that locks me out of my OS in a more "constructive" way. My thoughts on using xxcopy to replace xclone in 98SE2ME: please see this thread: http://www.msfn.org/board/?showtopic=46349...ndpost&p=352719 Hope this helps.

R u trying to find more work 4 me? [just kidding ]Thanks for your advice. I actually plan [sometimes in the future when I'll find the time] to change the entire backup procedure for options 1 + 2, and avoid backing up the entire 98SE OS. Will slim it down to back up only the files that will be replaced by WinME files, plus the registry [*.DAT] files. This will also save time + disk space. And I'll probably use the plain DOS based COPY command [built into COMMAND.COM] to do this, and do away with xclone or other similar tools. This will also reduce the size of 98SE2ME.EXE. I've read the xxcopy license, and I don't think the author will make an exception just to let me use it in 98SE2ME. ;( Besides, xxcopy.exe is huge [~ 268 KB in size], and I need to think of everybody, including the people who still use dial-up/analog/56k modems. But I'll take look at DOSLFNBK, and maybe I find a way to use it to backup the LFNs. The good part is that I don't need to backup C:\Program Files [i never did], which would be a major pain, due to its many LFNs that would be "translated" into wrong ~1 ~2 etc SFNs. Besides, as far as I recall, all 98SE files replaced by ME files that I need to back up have SFNs [except the few from %windir%\WEB\Wallpaper = which are now backed up before installing option 3], and that makes it so much easier to use a primitive tool like MS COPY command. Hop this helps.

Try this new edition, guys. Most of the bugs should be fixed now. Eck: I can't reproduce the sysdm.cpl error not being copied to %windir%\system you experienced. Maybe it happened when u interrupted the batch file operation... [?] Please do not interrupt the batch files, even if u don't see anything on the screen, because you will experience errors, or even worse, data loss. As far as I can tell, none of those batch files will freeze your OS, their code is designed to let them complete, even if errors occur, and so far I haven't seen any errors on my PC [i just spent 2 hours testing options 1, 2 + 3 using the 7-14-2005 98S2ME edition posted below]. Let them finish, it's much easier to fix something afterwards from within Windows, and even if u can't fix something, just let me know, and I'll help u do it. If u would like to see exactly what those files do, please open them in Notepad. They all reside into C:\9!M . DOS blank screen upon reboot is normal, I have added "CTTY NUL" + "CTTY CON" into some of the batch code to suppress screen output. I found annoying starring at a listing of files being copied/moved/renamed/deleted. 98SE2ME cannot [even if I want to] implement the "hidden" DOS mode from WinME, because it is "hardwired" into WinME [a.k.a. MS-DOS 8.00] IO.SYS, COMMAND.COM + REGENV32.EXE, and 98SE or any other release, will lock up if u replace those files [except regenv32.exe, which doesn't even exist in 98SE]. DOS mode operation [after reboot] may seem different [eventually slower] because I have added more batch code, which means more files are moved/copied/deleted/renamed/etc around. VWIMaster: I was able to reproduce the "WiaMgr" thumbnail view errors u experienced, and which occurs ONLY IF u install option 3. A Google search and an hour later, I can tell u that it is due to a bug in WinME Movie Maker [C:\Program Files\Movie Maker\MOVIEMK.EXE], a tool which is installed and can be used *only* by WinME OS [i can't add it to 98SE2ME without further research, because it is tied up into other apps/tools/DLLs, specific only to WinME OS]. The WinME only fix is to install MS hotfix Q262806 [available only from Windows Update], listed here: http://www.mdgx.com/web.htm#WME So I removed all buggy JavaScript code from IMGVIEW.HTT, and copied it over into %windir%\WEB . Your original 1 is backed up as %windir%\WEB\IMGVIEW.HTO . If u would like to see the IMGVIEW.HTT changes I made, please open C:\9!M\IMGVIEW.HTT into Notepad. There was also more buggy code into imgview.htt which was tied up to scanners + digital cameras image transfer + slideshow, which is used + installed by ME, and known as WIA [Windows Image Acquisition] Manager, another tool specific only to ME OS. WIA Manager is also tied up into Movie Maker. Note that every time u run [after u installed option 3]: regsvr32 /s %windir%\system\webvw.dll IMGVIEW.HTT will be overwritten with a buggy copy from within WinME vebvw.dll. If that happens, please copy the "good" 1 from C:\9!M over to %windir%\WEB . Note that most files from %windir%\WEB are HRS [Hidden, Read-only, System], and u need to change their attributes to remove RHS [example]: attrib -H -R -S %windir%\WEB\*.HTT in order to be able to overwrite them. randiroo76073: From now on SFC.EXE info [inside default.sfc] is updated upon next reboot with all newly installed WinME system files. Have fun.

As far as I know SNMP Agent is already included with 98FE/98SE/ME. But u need to install this security update: Microsoft Windows 95/98/ME SNMP Unchecked Buffer SNMP.EXE + SNMPAPI.DLL Security Vulnerability Fix: http://www.microsoft.com/technet/security/...n/ms02-006.mspx Direct download [160 KB, English]: http://download.microsoft.com/download/WIN.../314147USA8.EXE More info: http://support.microsoft.com/?id=314147 How to install SNMP.EXE + SNMPAPI.DLL Fix on Windows ME: 1. Create C:\TEMP (example) from a DOS box: MD C:\TEMP 2. Download Patch (see above) into C:\TEMP. 3. Run (example using C:\TEMP as target folder) to extract files: 314147USA8.EXE /C /Q /T:C:\TEMP 4. You MUST disable System Restore: open Control Panel -> System -> Performance tab -> File System -> Troubleshooting area -> check the "Disable System Restore" box -> click OK -> reboot. 5. Download + install CoolKill [797 KB, freeware]: http://www.prowebsitemanagement.com/downloads/coolkill.zip 6. Run COOLKILL.EXE -> right-click on the CoolKill icon in Taskbar Tray -> highlight STMGR.EXE -> left-click on it to terminate this process. 7. Copy SNMP.EXE + SNMPAPI.DLL from C:\TEMP to %windir% (usually C:\WINDOWS) + %windir%\SYSTEM: XCOPY32/H/R/Y C:\TEMP\SNMP.EXE %windir% XCOPY32/H/R/Y C:\TEMP\SNMPAPI.DLL %windir% XCOPY32/H/R/Y C:\TEMP\SNMPAPI.DLL %windir%\SYSTEM 8. You may want to reenable System Restore: open Control Panel -> System -> Performance tab -> File System -> Troubleshooting area -> uncheck the "Disable System Restore" box -> click OK -> reboot. 9. Delete C:\TEMP. Also, an older version is posted exclusively for Windows 95: Microsoft Windows 95/OSR1/OSR2 SNMP Agent allows to monitor remote SNMP connections: http://www.microsoft.com/windows95/downloa...s/w95snmpagent/ Direct download [67 KB, English]: http://download.microsoft.com/download/A/D...9/W95snmpzp.exe But MS recommends not to install SNMP Agent on 98/ME. Please note that Win95 SNMP Agent installs older versions of INETMIB1.DLL + SNMP.EXE. These files [together with SNMPAPI.DLL] are already installed by 98/ME [all editions]. If u wish to install 95 SNMP Agent anyway, u can do so, but do not allow the older files to replace the newer ones you may already have. Run W95snmpzp.exe and then read SNMP.TXT to learn how to install it from Control Panel -> Networks. Hop this helps.

To be really up to date, you also need to install MDAC 2.8 SP1, MSXML 2.6, 3.0 + 4.0 current editions, MS Jet 4.0 [if u use MS Office components], WMI, MSI Installer, ADS Client, MSAA, and a few others, which u can find here: http://www.mdgx.com/add.htm and here: http://www.mdgx.com/ietoy.htm Then, of course, u need DX 9.0c [+ DX.CPL]: http://www.mdgx.com/dx.htm and WMP9 [+ WMFDIST.EXE to get WMP10 Codecs]: http://www.mdgx.com/wmp.htm but I'm sure u already installed those. Hope this helps.

Looking forward to trying your new DOS Help. If you like, I can upload it at my site. Just let me know if ok with you. Keep up the good work. Best wishes, MDGx

? -that only happens the very first time it's run, to install it, in my experience... after it's installed, it never happens again, no nag, no extra keystrokes, and it also has additional switches for more automation of any prompts/defaults, too... (here comes more xxcopy praise : I've found xxcopy to be extremely simple (the /clone switch does pretty much everything ya need), and very fast (if HD is defragged, often get 20mb/sec true copy transfer rate, and that's with 5000-10000 files copied; not bad at all)) I think we're confusing terminology here: LFN compliant means it preserves the "long" filename, but does it ALSO ALWAYS preserve the SHORT (8.3) filename which is associated with the LFN? Windows itself does not, when copying files/folders in explorer; -Are u familiar with that classic win98 flaw, I call it the tilde ("~") flaw? This is what I'm talking about, keeping the 8.3 name & the LFN properly associated (if ya copy 2 or more files that have similar short names, like MICROS~1.TXT, and MICROS~2.TXT, at the same time to another directory, it sometimes SWITCHES the short (8.3) filenames, depending on which file it happens to create first... -same thing happens when unzipping files, the short name's "~1,~2", etc, are completely arbitrary, NOT necessarily the same as when ya zipped it up, they (8.3's) are numbered by the new file creation order only... it's a famous flaw, the reason for which DOSLFNBK was created (and is probably much better explained at it's web site)-and, with my testing, every zip/copy/backup prog (FREE, anyways), have failed to keep the proper association between 8.3 names & LFN's in some cases, making them useless for reliable backups (and believe me, I was SHOCKED when I discovered this, about 1 or 2 yrs ago... I couldn't believe it was so prevalent, so flawed, everywhere! ) I'm not trying to convince you that xclone is better than xxcopy [obviously, your favorite], because it's not, I'm only trying to tell you that there are other tools to consider out there that have merit, depending on user's purpose.More like this: http://short.stop.home.att.net/freesoft/filutil1.htm#move From my point of view [for example, building installer packages like 98SE2ME], I need a simple tool to do the job fast from batch files, the same time be of small file size *and* have a freely distributable license. Guess what, xclone has all that, xxcopy doesn't. The only way to force xxcopy not to display its annoying copyright multiscreen slow-scrolling message is to delete INSTALL.BAT and add UIXXCOPY.BAT into the directory where the XXCOPY.EXE executable resides, which is exactly what it does when u 1st install it [note that XXCOPY16.EXE only works in native DOS mode (16-bit, no LFNs), and if u don't use native DOS mode, u can safely delete it]. But the moment u delete UIXXCOPY.BAT, it will display that message all over again. And that is not acceptable, if looking at this from my point of view, of using such tool with installers like 98SE2ME, because I'm not going to add a useless batch file only to prevent xxcopy's messages. Then if u compare their sizes: - xxcopy.exe 2.85.9 [current ver] = 274432 Bytes - xclone.exe 1.3 = 22916 Bytes again, unacceptable. And if u look at the distributable license, you'll see that xxcopy.exe cannot be bundled by itself [single file] with other distributable packages, but xclone can. Again, unacceptable. Talking about the speed at which such tools perform in native DOS mode: they copy/move/etc files/folders as fast as your CPU, HD controller + HD are, no matter what else u do. In Windows mode, that's an entirely different matter, because different disk/file/folder manipulation tools are not the same, some are built to take better advantage of certain Windows features. And I presume, because xxcopy is a more sophisticated tool, it most certainly performs faster in this respect. But in the native DOS world, all such tools are equal, and if u time the same cloning operation using both [let's say copy entire Win98SE OS to another drive/partition], you'll see that completion times will be almost identical, depending mostly on the cluster location on HD of respective files at the moment of initiating the copy operation. Of course, you can use SMARTDRV to speed this all up, but u won't notice any difference between the two if u use the same SMARTDRV command line switches with both. Another factor to consider is file copy verification, because if it is turned on, the whole operation slows down considerably. About LFN standard compliance/preserving: SFNs [short File Names] = MS-DOS 8.3 [file naming convention] are always associated with LFNs in MS Windows 32 and 64 bit [a.k.a. Win32 and Win64 = that include all 9x + NTx OSes] environments, otherwise the entire HD would not be readable. And all tools that deal with LFN/SFN file operations must comply to preserve both. That implies their indelible association, because a LFN file in MS Windows world cannot exist without its SFN counterpart. It is not the tool's fault if LFns are lost, but u can blame the [early] Windows 9x/NT4 OSes, especially original Win95 for this, and poorly programmed setups [including Microsoft's own], INFs, REG files, tweakers etc... that do not account for this "filename truncating" feature. More info: http://www.mdgx.com/newtip9.htm#NUMTAIL Please note that MS lists only 9x + NT4 OSes as affected by this "glitch", not 2000, XP or 2003. Therefore the way Win9x generates 8.3 SFNs "aliases" from LFNs [not their association], is an entirely different matter. That's why I have added a combination of VBScript + DOS batch code into E0!X.BAT in order to make sure this doesn't happen, no matter what 8.3 [short name] the "C:\Program Files" folder might have on any computer 98SE2ME would install files to. To avoid this problem altogether, I've also replaced all "C:\PROGRA~1" instances in my registry with "C:\Program Files", and also fixed all other similar folder names. And because of this WinOS limitation [sequentially generating 8.3 "aliases" upon file/folder creation], any copy/backup/restore tool based on standard filecopy command would behave the same way. And you're right, DOSLFNBK is one of the few that preserves LFNs properly because it uses a completely different approach. Hope this helps.