jaclaz

You mean the .inf, not the .sys . This basically means: [Manufacturer] %INTEL%=INTEL_HDC,ntx86 Look in sections: [INTEL_HDC] and [INTEL_HDC.ntx86] depending on the OS. Then in this: [INTEL_HDC] [INTEL_HDC.ntx86] %PCI\VEN_8086&DEV_27C3&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_27C3&CC_0104 %PCI\VEN_8086&DEV_27C6&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_27C6&CC_0104 %PCI\VEN_8086&DEV_2822&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_2822&CC_0104 %PCI\VEN_8086&DEV_282A&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_282A&CC_0104 the INTEL_HDC section is empty, but Windows 2000 will try loading that one. So - at least in theory - this should do: [INTEL_HDC] %PCI\VEN_8086&DEV_27C3&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_27C3&CC_0104 %PCI\VEN_8086&DEV_27C6&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_27C6&CC_0104 %PCI\VEN_8086&DEV_2822&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_2822&CC_0104 %PCI\VEN_8086&DEV_282A&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_282A&CC_0104 [INTEL_HDC.ntx86] %PCI\VEN_8086&DEV_27C3&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_27C3&CC_0104 %PCI\VEN_8086&DEV_27C6&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_27C6&CC_0104 %PCI\VEN_8086&DEV_2822&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_2822&CC_0104 %PCI\VEN_8086&DEV_282A&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_282A&CC_0104 jaclaz

So, the only way out - maybe - is to make the two alternative ETD.inf's, it might mean that for *some* reasons the ETDUIsimple.exe needs to be installed by the Setup.exe, but this makes NOT any sense , as earlier in tests you had not any ETDUIsimple.exe in the ETD.inf and you plainly copied it manually to the \Program Files\Elantech\ folder, there must have been something that you did that made it work. Or maybe the two Registry settings: CustomerDefinition=4 UI_ThemeOption=4 need to be set at 5 at install time and can only be changed later. Another possibility is that for *some* reason the ETDSimpleUI.exe needs a number of keys pre-made and these keys are actually created NOT by the ETD.inf, but rather by the Asus_UI.exe. I think the only way to understand that you need to trace the ETDSimpleUI.exe as it is now (not saving settings) and then uninstall everything, re-install with the "original" method (first install the 11.5.20.3 and then replace manually files) and see (if now the ETDSimpleUI.exe works, saving settings). jaclaz

Maybe there needs to be "more" keys in HKCU , anyway I think that a possible way out at this point will be to make two different "monolithic" ETD.inf's, both to be installed (the one or the other) via Setup.exe. The first, the current one, without the ETDSimpleUI nor any .avi files. [1] The second including the ETDSimpleUI and the .avi files. [2] It is possible that the "key" is again in the two Registry settings: CustomerDefinition=4 UI_ThemeOption=4 (those that are in the Samsung driver, from which the ETDSimpleUI comes from). Try changing those two keys and try again (probably you will need a reboot). If this works, these can be added to the ETDSimpleUI.inf and keep it "self-standing". Change in the ETDsimpleUI_remove.inf this line: HKLM,Software\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel\NameSpace\{3EA22083-D5BF-411b-A6D6-A27541794266},,0x00000000,"Elan Control panel" to: HKLM,Software\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel\NameSpace\{3EA22083-D5BF-411b-A6D6-A27541794266} (my bad). Do also this test: copy manually the ETDsimpleUI_remove.inf to the \Program Files\Elantech\ folder uninstall the driver via the ETD_uninst.exe Is the \Program Files\Elantech\ folder deleted anyway AND is the Control Panel icon/etc. also removed? jaclaz [1] and with the two keys set to 0 [2] and with the two keys set to 4

Good. Back to this test, and if it works, we are all set for a "final" version: https://msfn.org/board/topic/181362-xp-driver-for-amd-hd8180-graphics-and-elan-ps2-touchpad/page/38/?tab=comments#comment-1182336 Note, when trying here (BOTH with devcon and with Setup.exe), there is a "queer" behaviour, they *somehow* install - besides ETD.inf, also ETDsimpleUI.inf AND ETDSimpleUI_remove.inf (which of course makes the ETDSimpleUI.exe install a non-install), it is like the Setup.exe (but also devcon.exe, notwithstanding the command line devcon install .\x86\ETD.inf *ETD0108) runs all .inf files in the folder, i.e. *.inf. The ETDSimpleUI.exe needs the .avi files that are present in the "main" \x86\ folder and even if we make an \x86\ETDsimpleUI\ subdirectory, the path to the higher level \x86\ subdirectory is not a valid one in .inf files syntax (AFAICT), not really a problem as the .inf will ask for the first .avi file and the user will need to point to the higher level directory, then all other .avi files will be copied from there. The ETDSimpleUI_remove.inf can instead be put in a subdirectory, no problem with that. We'll have to think about a way out for this CATCH22 , we could well replace the two .inf files with a small batch or a couple .reg files. Also, it has to be tested if the ETD_Uninst.exe is "smart" or not, i.e. if it deletes ONLY the files mentioned in oemnn.inf AND IF the \Program FIles\Elantech\ directory is empty THEN it removes it OR if it simply deletes the \Program FIles\Elantech\ directory, no questions asked. About ETDSimpleUI.exe, it seems like in order to run it needs to access an (empty) HKEY_CURRENT_USER\Software\Elantech key, this is not (here) created by the ETD.inf (but it may well be created on your system by the actual ETD.sys or ETDCtrl.exe running, cannot say). jaclaz

Yep , in the Frankendriver tests we used as base the 11.5.20.3 and either deleted unneeded files or overwrote selected/needed ones from 11.4.14.1 (or from some other older "Asus" drivers), so - at least here - the Setup.ini in use remained (or became) the *catch all*: [Setup_Config] CheckHWID=1 ResetPreviousRegistry=1 Anyway, it is an interesting philological experiment, undoubtedly the "base" (original) Setup.ini is something like: [Setup_Config] CheckHWID=1 CheckMode=1 String1= ... Stringn= ResetPreviousRegistry=1 the (diligent) Lenovo guy filled the blanks, the (lazy) Asus guy removed the CheckMode and Stringn lines, the (lazier) Samsung guy changed only the CheckHWID=0. Three different solutions/workarounds for a non-problem (as AFAIK a .inf for a driver won't install anyway if it doesn't find the hardware - hence the need for me to create the device via devcon) . The difference is AFAICT only that the Setup.exe outputs a "Cannot install" window earlier if the hardware is checked (CheckHWID=1) and if the list is in Setup.ini (and CheckMode=1). jaclaz

A (oldish, circa 2012) link casually dropped out of my bag o' links: http://reboot.pro/topic/17655-boot-into-3rd-party-efi-application-via-bcd/ anyone wanting to read it may learn something. jaclaz

I don't know, that should be it, BUT (I guess) that IF: CheckMode=1 the Stringn= entries in the Setup.ini are checked (instead/overriding ETD.inf ones or - more likely - as a pre-requisite). My personal vote is on the "exact" (for what it costs) Setup.ini: [Setup_Config] CheckHWID=1 CheckMode=1 ResetPreviousRegistry=1 String1=*ETD0000 String2=*ETD0101 String3=*ETD0102 String4=*ETD0105 String5=*ETD0106 String6=*ETD0107 String7=*ETD0108 String8=*ETD0109 String9=*ETD010A String10=*ETD010B String11=*ETD010C String12=*ETD010E String13=*ETD010F String14=*ETD0111 String15=*ETD0112 String16=*ETD0113 String17=*ETD0114 sometimes (not always, but often enough) it is gratifying to be plus royaliste que le roi : https://www.oxfordreference.com/view/10.1093/oi/authority.20110803100332506 jaclaz

The Disk Manager in Windows 7 (and later) is quite good, and - even if a tad bit complex to use - Diskpart (also built-in) can do even more things, there is no need for a third party partition manager normally. About the dual boot, basically: 1) the boot related files for XP and earlier are NTLDR and BOOT.INI 2) the boot related files for Vista and later are BOOTMGR and \boot\BCD The normal booting sequence of XP is: MBR->PBR of active partition->NTLDR->BOOT.INI (choices)->Windows XP The normal booting sequence of Vista (and later) is: MBR->PBR of active partition->BOOTMGR->\boot\BCD (choices)->Windows Vista+ The normal bootng sequence of a dual boot like yours is: 1) MBR->PBR of active partition->BOOTMGR->\boot\BCD (choices)->Windows Vista+ 2) MBR->PBR of active partition->BOOTMGR->\boot\BCD (choices)->(NTLDR)->BOOT.INI-> XP The NTLDR is between brackets because it depends on the specific item and on the Windows version if it is used or not. Without knowing the specific, exact situation of your system (now and how it will be) it is not possible to provide you with exact advice on what to do. Your best choice would be to use BootIce that can manage the PBR's, the NTLDR and BOOTMGR and the settings files BOOT.INI and \boot\BCD via a nice GUI: http://reboot.pro/topic/21956-bootice-v1332/ you want the 1.332 version, but you will need to learn a bit about the principles and the usage of the tool. Depending on the exact setup, you may also want to introduce a separate boot manager (grub4dos) as primary boot manager, that would allow to have the two systems (XP and 7 or 8.1) completely independent. jaclaz

Very good. Yep, that "Lenovo" setup.ini is an "exception" as all the "Asus" ones are *just*: [Setup_Config] CheckHWID=1 ResetPreviousRegistry=1 Whilst the "Samsung" one is: [Setup_Config] CheckHWID=0 CheckMode=1 String1= String2= String3= String4= String5= String6= String7= String8= String9= String10= String11= String12= String13= String14= String15= String16= String17= String18= String19= String20= String21= String22= String23= String24= String25= ResetPreviousRegistry=1 Good catch . Though adding the "String28=*ETD0108" is a nice solution, it would cover only the ETD108, whilst the .inf - in theory - at the moment covers: *ETD0000 *ETD0101 *ETD0102 *ETD0105 *ETD0106 *ETD0107 *ETD0108 *ETD0109 *ETD010A *ETD010B *ETD010C *ETD010E *ETD010F *ETD0111 *ETD0112 *ETD0113 *ETD0114 so, since we have anyway to provide the modded ETD.inf we can add a pre-made simple Setup.ini file either according to the "Asus" philosophy (lousy/loose): [Setup_Config] CheckHWID=1 ResetPreviousRegistry=1 a (lousier/looser) "one size fits all": [Setup_Config] CheckHWID=0 ResetPreviousRegistry=1 or an "exact" one: [Setup_Config] CheckHWID=1 CheckMode=1 ResetPreviousRegistry=1 String1=*ETD0000 String2=*ETD0101 String3=*ETD0102 String4=*ETD0105 String5=*ETD0106 String6=*ETD0107 String7=*ETD0108 String8=*ETD0109 String9=*ETD010A String10=*ETD010B String11=*ETD010C String12=*ETD010E String13=*ETD010F String14=*ETD0111 String15=*ETD0112 String16=*ETD0113 String17=*ETD0114 jaclaz

Sure , I would say it is "normal". The prefetch folder is where Windows automagically creates *something* (let's call for the moment this *something* "links") connected to frequently used executables. Cmd.exe and Timeout.exe are the command processor (that runs the batch) and the command you used in the batch, conhost.exe is as well connected to the command processor (it is the console host) and dllhost.exe (likely, haven't checked) is connected to timeout.exe (or as well to cmd.exe). If you don't want them to be recreated you need to disable prefetch: https://www.technipages.com/windows-enable-disable-superfetch It may also depend on its actual setting, check the values in: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\Memory Management\PrefetchParameters EnablePrefetcher EnableSuperfetch https://www.tomshardware.com/reviews/ssd-performance-tweak,2911-5.html jaclaz

It is possible that (one way or the other) you managed to make a "dual boot system" or actually more a "dual boot single system", tha can boot BOTH in BIOS and in UEFI mode. Files used are different, in BIOS: \BOOTMGR \Boot\BCD vs. \EFI\Microsoft\boot\bootmgfw.efi \EFI\Microsoft\Boot\BCD In the booted system you should be able to see if you booted BIOS (please read as CSM) or UEFI, on 7 you will need to check SetupAct.log: https://www.eightforums.com/threads/bios-mode-see-if-windows-boot-in-uefi-or-legacy-mode.29504/ jaclaz

And what have you tried (that presumably did not work as you expected)? Or is the request slightly different, more *like* "please write for me a batch that does this ..." Anyway, see if any of the solutions here fits your usage: https://stackoverflow.com/questions/6836566/batch-file-delete-all-files-and-folders-in-a-directory Easiest is to use RD and the re-create the "base folder", but it is to be seen if that is OK in your situation (basically the recreated "base" directory will have a different creation date", Additionally if the volume - as it is likely the case - is NTFS, there might be the need to check for hardinks before deleting files unconditionally . jaclaz

Good , but for further tests you need to imagine being a "final" user, knowing nothing of this thread and that follows these instructions: 1) get the tp118w7 from https://support.lenovo.com/cz/en/downloads/ds035770 2) use Universal Extractor (or maybe easier use http://innounp.sourceforge.net/ ) to extract the contents, innounp -x tp118w7.exe 3) replace the ETD.inf in the directory \{app}\Elantech\11.4.14.1\X86\ with the new one 4) run the Setup.exe in \{app}\Elantech\11.4.14.1\X86\ Then, optionally, 5) get the Samsung driver 4.9.0.0 from https://www.helpjet.net/Fs-52207751-65343120-34459956.html 6) open it in 7-zip and copy the ETDSimpleUI.exe from \Elan\X86\ to the directory \{app}\Elantech\11.4.14.1\X86\ 7) Add the two ETDSimpleUI .inf files and right click/install the ETDSimpleUI.inf This is interesting , as it means that the Uninstaller likely has a number of "internal" settings that are not in the ETD.inf. It has to be seen if it does everything in the actual .inf. Try in the .inf: 1) add: ETDSys.DelFiles = 12 ; Driver directory at the end of: [DestinationDirs] 2) change: DelFiles = No_Files to: DelFiles = ETDSys.DelFiles in: [Uninstall] 3) add: [ETDSys.DelFiles] ETD.sys,,,0x00000001 after: [No_Files] 4) add: HKLM,"SYSTEM\CurrentControlSet\Services\ETD" at the end of: [Uninstall_DelReg] jaclaz

Ok, in the meantime the ETDSimpleUi.exe install and uninstall files. Expand the .zip in the "source" 11.14.4.1 directory together with the drivers files and add the ETDSimpleUI.exe, and right click->install on the ETDSimpleUI.inf. Of course the driver needs to be already installed. Then, to remove, right click->install on the ETDSimpleUI_remove.inf It remains the doubt about these .avi files: Button_SmartPad.avi Clicking_2F.avi Scroll_Reverse_H.avi Scroll_Reverse_V.avi i.e. if they are actually used by ETDsimpleUI.exe or not. jaclaz ETDSimpleUI.zip

Good. But the file is in the actual "untouched" \tp118w7\{app}\Elantech\11.4.14.1\X86\, right? It was missing in your "frankendriver" folder only because of all the various tests. Yep, and - additionally - it leaves the \Program Files\Elantech folder untouched AFAICT (and also the .HKLM\System\CurrentControlSet\Control entries ) The issue might be how the ETD_Uninst.exe behaves, i.e. if it executes the commands in: before or after: 1) having stopped or killed the ETDctrl.exe <- if it does this 2) having uninstalled the device (and having deleted the \WINDOWS\system32\DRVSTORE\etd_<stupid_long_string> and the \WINDOWS\inf\oemnn.inf :unsure:) When using devcon.exe/manually you *need*: 1) devcon remove *ETD0108 2) devcon dp_delete C:\WINDOWS\inf\oemnn.inf 3) rd /s C:\WINDOWS\system32\DRVSTORE\etd_<stupid_long_string> 4) taskkill /F /IM ETDCtrl.exe 5) rd /s %ProgramFiles%\Elantech And then remove the various Registry entries. Maybe this can be done with a batch and DPINST.EXE (which we already have in the tp118w7), I'll have a look at it. jaclaz

I guess you will need something newer if your intention is to confuse (maybe you meant surprise?) me. That Sprites Mod hack is what ? 2013? , and anyway is very little confusing, as a matter of fact (like BTW most of the things written by Jeroen Domburg) it is extremely simple and can be followed relatively easily. jaclaz

Ok. Attached ETD_XP2.inf (70 KB, slightly smaller than the original 1940 or so ) I set it to: DriverDate = "03/05/2013" DriverVersion = "11.0.0.31" to reflect the actual data of the used ETD.sys. ETD_XP2.inf , renamed to ETD.inf and copied to the expanded \tp118w7\{app}\Elantech\11.4.14.1\X86\ thus replacing the existing ETD.inf, should install fine the "basic" driver and functions. Try it after having cleaned/checked the Registry (just in case of leftovers from previous tests). See if it works. I concur that the only "pretty" control panel that makes sense is the ETDSimpleUI.exe, I will make a separate .inf (that of course will need the ETDSimpleUI.exe file from the Samsung driver, as - seemingly - all the .avi's used by ETDSimpleUI.exe are already in the 11.14.4.1). jaclaz ETD_XP_2.zip

Good , which is actually called "track". And right when you think you got the concepts right let me confuse you with geometry and the way it is "shielded" by the disk hardware: https://blog.stuffedcow.net/2019/09/hard-disk-geometry-microbenchmarking/ jaclaz

WHICH circle? Almost a cluster is a bunch of sectors addressed as the smallest unit of storage in a file system. What the file system driver does may depend on a number of factors, do not assume too much. Not really a block ( or sector) is the minimal addressable unit on device, it is not arbitrary at all, it is hardcoded in either the device or in its driver, for all it matters its size is normally 512 bytes but can be also 4096 bytes (newer disks). Again, do not assume too much, you can write a single byte to disk just fine. This is irrelevant (the two together). The stripe size is always a multiple of clusters, whilst stripe size may (marginally) matter for performance in a RAID 0, 2, 3, 4. 5, etc. i.e. in "striped" sets, (and it has no influence on Raid 1), it is a separate parameter from cluster size, which should be chosen as the "best possible" for the data to be managed independently from stripe size. About stripe size: https://www.tomshardware.com/reviews/RAID-SCALING-CHARTS,1735-4.html The rule of the thumb is however that the larger the stripe size, the faster the data transfer is, but this may also depend on the specific (software or hardware) setup. About cluster size, more or less the same rule of the thumb applies, the larger the cluster size, the faster the data transfer will be BUT in the case of smaller files there will be more "slack" space (wasted space), so you need a compromise. Since you are limited to FAT32 AND you have volume >32 GB you are "forced" to have cluster size 32K (and no, don't think that making two volumes with cluster size 16KB will change anything in a noticeable amount, it will be only very slightly slower). Then for stripe size, use the largest you are allowed to. jaclaz

Yep , that could be a good alternative, and - like the one above - could be an option, for the people that are not satisfied by the "standard"with ONLY files from 11.4.14.1. Summing it up: 1) new "base" ETD.inf that installs (hopefully) a working driver from 11.4.14.1 ONLY 2) optional .inf's that adds (hopefully) any among these (renamed to OEMElan.exe): Asus_UI.exe -> Asus_UI.inf ETDAniConf.exe -> ETDAniConf.inf Lenovo.exe -> Lenovo.inf DellTpad.exe -> DellTpad.exe ETDSimpleUI.exe ->ETDSimpleUI.exe ToshibaTp.exe ->ToshibaTp.inf and makes the added Control Panel item to launch it (basically it is several copies of the same inf with just the name of the .exe changed AND the relative .avi's [1]) 3) optional ETDUI.inf that adds (hopefully) ETDUI.cpl and and makes the added Control Panel item to launch it Back to work, what about: jaclaz [1] this (finding which .avi "belongs" to which .exe) might be the most work, I managed (somehow) to have the ETDSimpleUI.exe run on my machine, and I already found that in the ETD_XP.inf three needed .avi's are missing (Edge_Scroll.avi, Edge_inertial.avi and Scroll_No_FreeScroll.avi), so (hopefully) the "final" list for ETDSimpleUI.exe is: Button_ClickPad.avi DnD01.avi DnD02.avi DnD03.avi Edge_inertial.avi Edge_Scroll.avi Rotation_Twist.avi Scroll_Inertial.avi Scroll_No_FreeScroll.avi Swipe_3F_Down_SwitchWnd.avi Swipe_3F_LR_PageupDown.avi Swipe_3F_Up_Computer.avi Tapping_1F.avi Tapping_2F_Middle_Button.avi Tapping_2F_Popup.avi Zooming.avi The list for Asus_UI.exe should be the one in the ETD.inf from Z11566 (since that is the 10.0.26 version that "works best" for you (no files in common with the above): 1F_Activate.avi 1F_Drag.avi 1F_Tap.avi 2F_Popup.avi 2F_Rotation.avi 2F_Scroll.avi 2F_Zoom.avi 3F_ReturnDesktop.avi 3F_SwitchPage.avi 3F_SwitchWnd.avi 1F_appbar_top.avi 1F_appbar_down.avi 1F_charmbar.avi 1F_changepage.avi 1F_applist.avi 1F_snapview.avi 3F_Changepage_tab.avi 2F_Zoom_all.avi The list for Lenovo.exe should be the one in the ETD.inf from tp118w7, but there are overlaps.

NO ideas. But I think we have determined that ETDAniconf.exe sucks (and sucks big) and that what we really want is the "built-in" "complex" control panel in ETDmcpl.dll, and all in all I find natural enough that clicking on the tray Icon brings up the Mouse Control Panel and from its "Elan" tab, pressing the Options brings up the settings. It is two or three clicks more, but it isn't that bad IMHO. The {3EA22083-D5BF-411b-A6D6-A27541794266} Control Panel namespace could be managed by a separate .inf or ,reg that might be useful to those that want to use either the Asus_UI.exe (BTW have you noticed how in the filemon log *every* .exe is looked for BUT the Asus_UI.exe) or the ETDSimpleUI.exe (or *whatever*). From what I understand, one could (optionally) add to the Elantech directory *any* of: Asus_UI.exe ETDAniConf.exe Lenovo.exe DellTpad.exe ETDSimpleUI.exe ToshibaTp.exe renamed to - say - ElanCPL.exe and import the .inf or .reg (pointing to the new name) to have one of them as an alternative (via the Cotrol Panel icon), not as a replacement, of the ETDmcpl.dll "complex" settings (best of both worlds). jaclaz

I don't know. The original .inf settings are for a .exe (Asus_UI.exe or ETDSimple_UI.exe). Try tracing with Filemon what happens in 3) : 1) open the mouse control panel 2) choose the "Elan" tab 3) click on the "Options" button Maybe a parameter is passed to the .dll? jaclaz

Good. We can then remove, besides the unused "control panel" files also the stupid .avi files. Yep, almost. But WHICH Registry entry? ONLY the UI_ThemeOption? I.e. do you have now: CustomerDefinition=5 UI_ThemeOption=0 If yes, try setting to 0 also the CustomerDefinition (only to see if it actually changes something). As a side note I suspect that a reboot is not needed, but stopping (Task Manager) and re-starting ETDCtrl.exe should do the same. And - in order to make a (hopefully) final ETD_XP.inf we need to take a standing in favour (or against) attmpting removing: 1) anything that is not "ETD_STD_Inst" <- this should make it (hopefully) functional (at least installable) for ETD 000,101-102,105-109,10A-114 2) anything related to pointstick 3) the [ETD_APOptimize.AddReg] section (whole (3a) or leaving some "key" entries, like Normal Desktop and Windows Explorer (3b)) 4) the [ETD_GestureAPHotKey.AddReg] (whole (4a) or leaving some "key" entries, like Desktop and Windows Explorer (4b) ) Personally I propend for 1/2/3b/4b. jaclaz

Sure it doesn't. Actually the whole HKLM\CurrentControSet hive does not exist outside the running system CurrentControlSet is a "volatile" path created at boot by the OS and it is a copy of either ControlSet001 or ControlSet002 (typically, but I have seen systems with ControlSet up to 025). To know which "real" hive is in use (or will be in use at next boot, check the HKEY_LOCAL_MACHINE\SYSTEM\Select key and its contents). Normally you only have two ControlSet's, 001 and 002 and you want to have EnableBigLba=1 on both. jaclaz

Yep. Speaking of names, I know a man with a wooden leg named Smith ... jaclaz