Cixert

I have tasted again with Windows Vista, I was wrong in some concepts @jaclaz The final test says: -Windows Vista RTM does not start with ntldr and boot.ini -Yes, any Windows Longhorn does, at least up to 5231, maybe Windows Vista can start with the Dual Longhorn charger (Bootmgr+NTLDR). -Windows Vista does not work in Fat32, I have achieved it almost install in Fat 32, cheating it. After the install menu "choose partition" I have formatted the partition of NTFS to Fat32 with Alt+Tab. Then look almost until the end. Just, at that final moment, this says "a critical component has not been installed, restart to repeat boot process" After restarting it says "missing bootmgr" despite being installed.

You commented on this in another thread. I don't remember the method I used to partition this hard drive. But I only use Windows 2000/XP and compatible programs. It is a mini notebook without CD ROM. I did it via external USB. Until now I was working with XP and I did not modify the partitions to install Longhorn, except to format the 2nd partition to NTFS and convert the 1st partition to NTFS from FAT32. On the 1st partition I don't install operating systems, I only have the boot files. I will try to see the MBR partition machine code, I remember some old tools. What I can contribute is that it is possible to fix Longhorn to only boot with ntldr by disposing of bootmgr with the Windows XP recovery console. And I seem to remember that I also did it in a test with Windows Vista RTM. I'm going to try Windows Seven now. Greetings

With i386 I mean that the installer is compatible with 386, it works at 16 bits. (the installer for the 16-bit versions includes the i386 folder and the 32-bit versions include the source and boot folders) I just verified that the Vista 6.0.5231 installer (the one used by Shorthorn) requires both bootmgr and ntldr (versions before 4000 only ntldr, 5000 and 5001 post reset only ntldr). It starts with bootmgr and the bootmgr menu appears but after choosing an OS it jumps to ntldr and boot.ini appears The system doesn't boot whether I delete bootmgr or ntldr. In addition, the version of ntldr is different from that of NT 5.1, the previous one is not compatible. Longhorn pre-reset versions (up to 4093) do not install on FAT32 but I just verified that this 5231 installer installs Windows on FAT32. What has surprised me, regarding your idea of not using the Windows Disk Manager, is that I have placed the hard disk in another computer and after running the Windows XP Disk Manager, all the disk partitions have disappeared, without performing operation. "Only booting Disk Manager" why? In addition, the same thing has happened with just starting Acronis Disk Director without performing any operation on the hard disk, why? I have recovered them with EaseUS Partition Master. Offtopic: For those who think of trying Longhorn and Shorthorn, it's not worth it, it's all problems and errors, nothing works and no support. In Shorthorn not even work 360 Extreme Explorer and neither@roytam1 browsers, except on Shorthorn 3706 -Longhorn based- and Shorthorn Main Develoment. Also I have tested One Core Api @Skulltrailon all Shorthorn versions besides Windows XP. Only it just got me installed on Shorthorn 3706 causing a lot of problems and no NT 6 compatible programs work. Blue screen is guaranteed in XP and the system is normally not recoverable. Great care. Shorthorn 3790 versions (Main Development) can not be installed from XP to another partition, so I have not been able to test.

Newer versions of Windows Longhorn do not use i386 but bootmgr. From what I remember reading, both Longhorn and Vista call ntldr and this version of ntldr checks to see if boot.ini exists or bootmgr exists with his boot folder. The problem happened in Shorthorn 4033. Now I have tried other versions and I have verified that the problem does not recur, it only happens in 4033. All Shornhorn versions -Longhorn based- use the installer of Windows Vista build 5231. But I had the question of how to repair the installation . I will try those third party tools. In the original Longhorn I have not had the problem, although I have not been able to complete any installation successfully due to different problems. Original Longhorn requires an NTFS partition to perform the installation.

I have tested all original Longhorns from a hard drive with 4 primary partitions. 1-Boot Files i386 boot.(boot partition). 2-Empty for the installation of the new system. 3-Windows XP x32 NT 5.1 4-Data I start the installation of the iso from Windows XP. No bootmgr based version has finished installing on my computer. I have tried the Shorthorn variant. This does install completely and the interface starts, but after the first reboot the message "ntldr is missing" appears. I have reviewed the files manually and they all seem correct. I have tried to recover the bootable boot from the Windows Vista recovery console command line but it does not recognize any Windows installation. The only way I've had to recover the boot has been from the Windows XP console with the "fixboot" command. Fortunately, the boot is recovered through boot.ini and Windows Longhorn star. How can you recover the original boot of Windows Longhorn? Preferably with command line or manually. I have not found any program that manages to recover the boot. EaseUS manages to recover MBR and partition table but does not fix boot. what does fixboot actually mean?

I have found a way to disable duplicate creation of 8.3 short names on FAT32 plus NTFS but this does not apply when it exceeds the 260 character path, in which case XP automatically renames long files to 8.3, when the folders are copied. This issue does not happen on Windows 2000. To disable: fsutil behavior query disable8dot3 1 To enable: fsutil behavior query disable8dot3 0 To check status: fsutil behavior query disable8dot3 https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/fsutil-behavior On the other hand, I have read here that it is convenient to disable the function of creating duplicate names.I don't know if this can cause problems, for example with tools to recover the system that work from CD-ROM or floppy disk. https://ttcshelbyville.wordpress.com/2018/12/02/should-you-disable-8dot3-for-performance-and-security/ BEWARE the commands of the last link do not apply in XP. (not to be confused with the NT 6 fsutil 8dot3name command) I have found the following tools to detect long paths: -Long Path Tool (also copies long paths) (demo) -TLPD (Too Long Paths Detector) -Path Scanner (trial 13 uses) -Robocopy, command to copy folders from Windows Server 2003 Resource Kit Tools

Links are down...

So there seems to be life after death :-) I have not found technical information about it, but I will tell my experience. Today, using Windows 2000 with an NTFS external unit per USB I started decompressing about 10 very large files, between 0.5 and 10 gib. In parallel I have put a 50 gib file from the Internet. Then the system, at a given time, has shown me a blue screenshot. *** STOP: 0x000000d1 etc Driver_irql_not_less_or_equal And nothing more. It has surprised me that the memory dump message did not appear, or any other message. So, when I was going to press the restart button, I have noticed that the external hard drive had the writing light flashing. Thus, I have left it for an hour in this situation. Of course, disconnecting the Internet in case the 50 gib file continued. I really wanted to wait to see what happened when I finished blinking the light, to see if the system showed more messages on the blue screen, but I have not had patience. When I have returned, seeing it in the same situation, I have not been able to wait any longer and I have pressed the restart button. The fact is that at the beginning of Windows, no error was found on the hard drive and the 10 files in the process of decompression had been completed 8. Therefore, it is evident that the system continued working despite showing the blue screenshot and did not go to state "Requiescat in Pace".

I had been on a computer with Windows 2000 SP3 for years working with USB 1.1 until today I found the solution to enable USB 2.0 The original driver was an ICH7 with the USB EHCI service. This gave code 10 error, the device has not been able to start at the USB of the motherboard. I was thinking that may not work EHCI at W2000 SP3 and that I would have to update to SP4, but this has not been necessary. I have update usbhub20.sys to version 5.00.2195.6655. and it work. In the device administrator I have chosen the driver "Intel Pci to USB Enhanced Host Controller" Then a new driver category has appeared named "Standar USB Hub" and this has automatically installed the Driver "USB 2.0 Root Hub" working perfectly on my computer. I have the question of whether there is any performance difference with USB EHCI. I would also like to know where to find the EHCI service in Windows 2000, since in Services.msc it is not.

ok, I thought that the double name was only in NTFS, I read that in FAT too. The problem is that when I copy and paste a file into a long path, that it exceeds the character limit. Windows XP automatically renames a file with a long name to a file with 8 characters. If XP does not achieve 8 characters it gives an error, but if it can it automatic renames. This does not happen to me in windows 2000, it always gives a long path error. Does it only happen to me on XP? This has been happening to me since 2001. is it possible to recover in the File Allocation Table the original long file name? Both in the console and in Total Commander it shows the short name of the renamed file. The registry entries you comment are fine

This is a problem that I have had without a solution for a long time, I use FAT32. When I copy multiple folders if any file has a name that exceeds the Windows file length limit then XP copies it without giving any error and changing the long name to a short one with 8 characters and "~" symbol. For example, if the file has the name: "program to read documents PDF.exe" Windows XP renames it without giving any error to: "program~.exe" Apparently the file keeps its real name somewhere, since a shortcut still finds it with the short name, but it prevents me from knowing the true name of the file. I would like to know how: 1-Be able to see the long file name again. 2-What Windows XP gives an error message when I am copying a file with a long name that exceeds the limit, instead of automatically changing the name. I don't have this problem in Windows 2000, so when I go to copy and paste a lot of files I have to restart and use w2K, which gives me an error that it can't copy long names instead of renaming them.

It's me, @AstroSkipper @mina7601 In my profiles folder I see 5 profiles. The newest profile is "jvsrhsc8.default-default-3" But in the profiles.ini file I see a mix of profiles. Is it safe to delete all profiles and leave the newest one? what should the profiles.ini file look like? What does locked=1 & isrelative=1 mean? Thanks. [InstallB2BEF67B3394E6F3] Default=Profiles/5j62w0ky.default-default-1 Locked=1 [Profile3] Name=default-default-2 IsRelative=1 Path=Profiles/gtdvt7r6.default-default-2 [Profile2] Name=default-default-1 IsRelative=1 Path=Profiles/5j62w0ky.default-default-1 [InstallC48CA6CD8F76FD36] Default=Profiles/c3s58rv4.default-default Locked=1 [Profile1] Name=default IsRelative=1 Path=Profiles/6ay5acid.default Default=1 [Install77095BA9BFBDBF19] Default=Profiles/jvsrhsc8.default-default-3 Locked=1 [Profile0] Name=default-default IsRelative=1 Path=Profiles/c3s58rv4.default-default [General] StartWithLastProfile=1 Version=2 [Profile4] Name=default-default-3 IsRelative=1 Path=Profiles/jvsrhsc8.default-default-3 [Install85442B1DBF4D6613] Default=Profiles/gtdvt7r6.default-default-2 Locked=1

Fixed: It was a worm. I use Service Pack 3 with the Blaster, Sasser & Conficker update packs, but on both computers I had been messing around with changing the hal and because of this old copies version of the hal layers were restored. On the desktop computer I fixed it by restoring copies of ntldr, hal.dll BOOTVID.dll and especially ntkrnlpa.exe Interestingly on this computer it worked by restoring a previous version copy of the hal layer and connecting to the internet did not reproduce the problem again. At that time I still did not know the problem cause. In the laptop that did not work for years, after resetting the registry, it stopped booting only after connecting to the Internet. I've restored a registry copy, reinstalled the updates anti-blaster, Sasser... And the problem has not returned. It is curious that neither Avast nor Malware Bytes detected any virus in the scan performed. On the other hand, the registry change comparator files showed different results when comparing both registries. But on the laptop they showed 2 very suspicious keys with FAT32 format. HKLM\SOFTWARE\Microsoft\Cryptography\RNG\Seed: AB 3C CD E7 5A 38 7D 97 07 0C F0 9F E6 6A B2 3F E8 EC 7F 61 06 98 D2 2E FA 3D 1A A4 52 54 40 7C 1F 43 E2 7A 9C 02 94 13 C8 64 9F D8 F8 20 19 35 50 A2 F4 6A DC 06 95 6A 1F A2 0E 1C 2F 53 1C F1 01 28 52 81 A7 51 39 91 A4 9A 85 06 2C B3 84 E9 HKLM\SOFTWARE\Microsoft\Cryptography\RNG\Seed: 97 93 BC 79 5D DE C2 4F C3 E9 0B AF F8 A7 90 B7 9D 16 EF E8 C0 F6 EB C1 8A 58 45 6A D6 B4 73 E2 03 9E B8 BB 75 50 4A 9F 28 9D B0 07 AE 64 6A 20 07 4B BB 13 20 F9 C0 F6 1D C7 DE 6D 94 7B A0 FC 12 EC 4D E0 BC 52 D8 00 1C 93 5E 0A 85 67 D6 74 edit For the exposed: -Desktop computer ---> The problem arises with or without an Internet connection. Fixed restoring ntkrnlpa.exe previous version -Laptop ---> The problem occurs only when the system is connected to the Internet. Fixed updating ntkrnlpa.exe After writing the previous lines I have gone to upgrade Windows 2000 on both computers with: -KB824146-x86 Anti-Blaster -KB835732-x86 Anti-Sasser -KB828741-x86 Anti-attack by RPCSS On the laptop I haven't had any problems, but on the desktop the problem returned after installing KB824146-x86 Anti-Blaster and restarting the system. I haven't checked if it updates ntkrnlpa.exe Then I went to install KB835732-x86 Anti-Sasser, but it gave me the error "The installation program could not verify the integrity of the Update.inf file" In Internet forums it says that it is because the encryption service is not running. I do not see this service installed in Windows 2000. It is possible that I have uninstalled it in the past. The problem has been solved by restoring a fairly old version of the registry, from 18 months ago, on which I have been able to install the updates.

sorry, the post was originally written in english from the computer. But I have gone to edit the post from the phone and when I hit send it has been automatically translated from English to Spanish. There is a problem with Chromium's automatic translators on smartphones and non-native language forums. I wanted to add that I have checked the Windows 2000 startup files, before loading SYSTEM. I am surprised that the file kdcom.dll says to load at startup without errors but this file does not exist in the Windows 2000 directory

He logrado iniciar Windows 2000. En este momento, las copias antiguas del registro no fallan después de reiniciar Windows 2000. La última copia del registro es la única que falla al reiniciar Windows 2000. Pero sé que, aunque el antiguo las copias funcionan ahora, en cualquier momento vuelve el error. Con los programas de comparación de registros no veo un cambio en el archivo SYSTEM que determine el error. Quizás alguien más lo vea. Nirsoft no funciona en Windows 2000. Lo he ejecutado en Windows XP, el problema es que no funciona para comparar el registro actual de Windows 2000, solo funciona con las copias. Nirsoft con las 2 últimas copias del registro https://anonfiles.com/42VbQ2F1y8/Nirsoft_jpg Regshot con las 2 últimas copias del registro https://anonfiles.com/S76aReF8yb/dos_ultimos_winrescue_txt Regshot con la última copia del registro que no reinicia y el registro actual de Windows 2000 que no inicia https://anonfiles.com/Ecq1RaFbyf/No_arranca_y_ultimo_winrescue_para_compartir_txt

Downgrade drivers. High resource consumption

The problem happened to me on a laptop a few years ago. Now the problem is on a desktop computer. After defragmenting, at this time without any further operations, even though I restore any registry copy, Windows 2000 does not start due to the error in SYSTEM. I have cloned a copy on another hard drive with R-Drive Image and it doesn't boot either. I have also created an image in a file and later restored it, with the same result. I can only think that Windows is not looking for SYSTEM in the correct path. how can i check it?

Thanks, with USB original box my 5TB Seagate disk with Windows 2003 drivers as GPT is limited to 2TB, but with any USB Logilink adapter it is not GPT limited, the problem is with MBR disk.

This is Chromium 57. You do very well not to install. This is very intrusive, it creates a service named knbcenter.exe that prevents any modification of the installed files, so it is no longer possible to put the English language. It also slows down the Windows XP startup. I have managed to uninstall it by translating the menu from Chinese. I have saved a installation copy and just by running it, it has installed everything again, it does not work as a portable.

The last version Windows XP compatible from Liebao Browser aka Cheetah Secure Browser aka Cheetah Safe Browser aka Kingsoft Browser is the 6.5.115.19871 from November 2021. It is possible download here http://www.liebao.cn/6/index.html New version is not Windows XP compatible.

Thanks, but I have copies of the registry made with WinRescue2000. After defragmenting it seems strange to me that after restoring a previous version of the registry sometimes it starts and sometimes it doesn't

The hard drive is 500 GB Sata II with 4 primary partitions in Fat32, in the second partition Windows 2000 is installed. The SYSTEM size does not reach 6 MIB. I have executed Chkdsk / f / r and has no errors. I have executed the Victoria test and does not find defective sectors. S.M.A.R.T. It is not very healthy, but it does not say that the status is critical, I have Windows XP in the third partition running without problems. I have defragmented the Windows 2000 partition and now the system does not start though I restore any registry copy complete. This says that all SYSTEM copy is damaged. Edit: After executing Victoria I can restore copies System file and I return to the initial problem

Sorry for not reading all previous conversations. I have not understood in the first post if to update the certificates it is enough to download the application or if it is necessary to follow the additional steps.

I would like to know what the 360 Extreme Explorer engine really is. In the interface it says Webkit. But the doubt enters when seeing that it runs Chromium 86. In my notes I had pointed out that this is webkit adapted to Chromium, but I have the doubt if 360 Extreme Explorer has a Blink engine. How is the case in other chromium browsers like DC Browser, Kafan MiniBrowser, Liebao Cheetah Secure Browser, Maxthon, QQ Browser, Sogou Explorer, UC Browser, TS Browser...? Do they have blink engine or webkit engine? I take advantage of the post to ask if it is possible that 360 Extreme Explorer does not change to the Trident engine, when it does not load a page the first time. I already have configured in settings to use only webkit, but sometimes it changes to the Internet Explorer engine.

I have 2 computers with the same problem, a desktop and a laptop. When starting Windows 2000 it says that the SYSTEM registry file is corrupted. I restore a previous registry backup made automatically with the WinRescue 2000 program and then Windows starts again. But when I restart the computer the problem returns. I think I don't have any rare software installed that I don't have on other computers. What can be?