Cixert
Content Type
Profiles
Forums
Events
Posts posted by Cixert
-
-
On 4/2/2023 at 1:20 PM, AstroSkipper said:
In terms of Protegent Antivirus, there is a review on Softpedia: https://www.softpedia.com/get/Antivirus/Protegent-Anti-Virus.shtml
To be honest, I never heard of this program before, though. But it seems indeed to be XP-compatible and quite well known in India (and probably in other eastern countries).
Anyway! Another option which has to be checked more deeply.
I'm trying alls antivirus software to make a short list.
Protegent Antivirus AV Cloud is not currently supported on Windows XP.
When trying to install it unpack 2 programs in c.\PAV
If it is done from XP, only Unistal-Date Care aka Crash Proof is installed, which claims to make copies of the software and is not an antivirus (it is not known what it really does, it does not give info, help, or options).
Danger. It seems that he takes all the information from your hard drive and sends it to his cloud.2 -
On 6/25/2022 at 2:23 AM, AstroSkipper said:
And a further tool associated with this AVG version is the AVG Clear 18.8.4084.0 to get rid of all installed components if necessary.
Download link: https://install.avcdn.net/avg/iavs9x-xp/avgclear.exe
Cheers, AstroSkipper
in that link
https://install.avcdn.net/avg/iavs9x-xp/avg_free_antivirus_setup_offline.exe
it downloads
AVG Antivirus Free 17.9.3761.0
In this link
https://install.avcdn.net/avg/iavs9x-xp/avg_internet_security_setup_offline.exe
it downloads
AVG Internet Security 18.8.4084.0
I understand that the Internet Security version is trial
Where can I download AVG Antivirus Free 18.8?0 -
The world is crazy...
1990 Symantec buys Norton.
2016 Avast buys AVG
2017 Norton buys LifeLock.
2019 Broadcom purchases Symantec security division and name but renamed NortonLifeLock.
2019 Accenture buys NortonLifeLock.
2020 NortonLifeLock purchases Avira through Investcorp.
2021 NortonLifeLock buys Avast creating Gen Digital as a merger.
https://www.itpro.com/security/cyber-security/360540/nortonlifelock-and-avast-to-merge-in-8-billion-deal1 -
2 hours ago, mina7601 said:
Well, after I put dwmapi.dll, it then complained about missing _except_handler4_common in msvcrt.dll, so I had to install this (use a translator, as this is a link to a Japanese site), and then, the error about missing _except_handler4_common in msvcrt.dll went away, but it then gave me this error I wrote about previously.
It worked for me just putting msvcrt.dll 6.0 next to adwcleaner.exe, I didn't have to install anything.
Much to my regret I have decided to install AVG 18.8 to analyze a 1 TiB disk with new content, I prefer not to try Avast 18 since I have happily installed Avast 6.0 with definitions of the year 2020.After reviewing the AVG options I don't see a default actions option.
After 67% I stop the scan and see that AVG has quarantined 70 files, it has extracted small files from large zip archives (100-1500 GiB) and quarantined them. Most classify them as Malware-gen, Evo Gen, or PUP. It has also qualified as key-generator virus some open source Linux files. AVG takes the law into its own hands and decides to quarantine any key-generators, even if these are not it.I want these files, so I look for the "restore" option, but since these are files belonging to ZIP archives, it is not able to restore them. I have had to restore these to an alternate path, unzip each zip and re-include the files.
OK, I hate AVG and any new program that annoys and wastes the user's time.
This has qualified files as viruses that no other antivirus detects in virustotal.com, it has even detected that Thorium Browser 109 SSE2_x86, the alternative Chromium version for Windows 7 supported by Google, is a virus.
Even so, I have continued investigating AVG and I see that within the folder analysis there is an option called "Actions" to establish that "no action is carried out" after the analysis.
I do a test with a couple of files with suspected viruses and it works.
So I decide to scan the entire USB hard drive (1 TiB). After 10 hours the analysis ends and "unpleasant surprise" I see that in 122 files with supposed viruses it has decided to send 31 to quarantine, because it feels like it, I don't see any other explanation, these don't seem like dangerous viruses.
So I have to restore these back inside the zip file that extracted them.
I don't remember if older versions of AVG behave this way.
Do you know if Avast 18 also behaves in this way?
Long live Avast 6.
https://msfn.org/board/topic/182157-end-of-avast-5-6-and-7-virus-definition-updates/1 -
1 hour ago, Cixert said:
The last version adwcleaner for XP is 6.047 (2017-05-19) and it does not have a cloud version.
In 7.4.2 before to see the error message in user32.dll I had to download and attach the dwmapi.dll v. 6.0.5384.4 to the installer.I am looking better and in options there is the local and server option. How can I know which database is being used? Using it offline does not give any connection error.
Edit:
Report after analysis
# AdwCleaner v6.047 - Archivo de registro creado 26/04/2023 en 04:50:38
# Actualizado en 19/05/2017 por Malwarebytes
# Base de datos : 2017-05-19.1 [Local]
# Sistema Operativo : Microsoft Windows XP Service Pack 3 (X86)1 -
1 hour ago, mina7601 said:
Can confirm, this is the error that appears
:
The last version adwcleaner for XP is 6.047 (2017-05-19)
https://download.toolslib.net/download/file/1/851?s=gP7VLih67fmmhqhqfLTpmYQR0FtB2J4p
and it does not have a cloud version.
In 7.4.2 before to see the error message in user32.dll I had to download and attach the dwmapi.dll v. 6.0.5384.4 to executable file.2 -
9 minutes ago, AstroSkipper said:
This thread is about antivirus programs targeting Windows XP SP3 only. Posting a list of antivirus programs targeting Windows Vista is not really helpful and rather misleading. There are a lot of versions inside this list which won't work under Windows XP SP3. Anyway!I know this list but it doesn't belong here. At least, you should change the headline to "AntiVirus & Security Software for Windows Vista". To answer your question, Malwarebytes Free v3.5.1 should serve perfectly your needs. I use Malwarebytes Premium v3.5.1 under Windows XP. It is the last version for Windows XP but still receives definition updates. Its detection rate is very good. Only the premium version has a background guard.
ok, I delete the list and leave the link.
My interest was to get a list by editing that one.2 -
1 hour ago, AstroSkipper said:
AFAIAA, unfortunately not. But the last months, I have presented some different antivirus or antimalware programs here in the thread and disseminated information about them, all still working under Windows XP.
I am looking for an antispyware type "adwcleaner", do you recommend any?
I have downloaded Zemana which claims to be compatible with XP but it really doesn't seem to be.
https://zemana.com/us/antimalware.htmlThere is a list for Windows Vista, maybe for XP it will be similar
2 -
Hello, is there a list of updated antivirus and antispyware for XP?
2 -
I have again installed Windows Vista Enterprise and the result is the same. When I write "Bootrec /Fixboot" when starting the hard drive the BIOS shows the message "A disk read error occurred" + strang symbols.
When executing third-party programs to modify partitions I see that the active partition C: FAT32 is not correctly recognized. These do not identify the format and name of the partition. This is only recognized by Acronis Disk Director and by Windows Disk Management, both from NT5 and NT6.
This begins in sector 63.I have formatted this active partition in Fat32 again and manually copy the boot files:
-From Windows XP ---> When restarting boot directly ntldr.
-From Windows Vista ---> Don't let it format it.
-From Windows Seven Console ---> When restarting boot directly Bootmgr.
-From Eassos Disk Genius 5.4 ---> When restarting boot directly Bootmgr.
-From Minitool Partition Wizard 7.8 ---> When restarting an intermittent cursor appears.
Then I execute "Bootrec /Fixboot" and starts correctly Bootmgr.
The same if I execute the command with the other options.
-From Minitool Partition Wizard 11.6 ---> When restarting an intermittent cursor appears.
Then I run "Bootrec /Fixboot" and returns the error "A disk read error occurred" + strang symbols.
The partition is again defective.
-From Minitool Partition Wizard 12.5 ---> When restarting an intermittent cursor appears.
The same errors as in version 11.6
This application, Minitool Partition Wizard, has ceased to be useful in its last versions.0 -
Writing /kernel=ntoskrnl.exe also begins Windows Vista from NTLDR to hal's error.
As I see that there are no people interested in this issue I do not continue to experiment with NTLDR.
I have restored the original files that I had replaced from Windows Vista and now I try to start this same Windows Vista from Bootmgr.
The Bootmgr menu appears to choose an operating system, I choose Windows Vista and the result is that now it seems that the same HAL problem happens as when I tried to start from NTLDR.
Now I try to repair the beginning of Windows Vista with the DVD.
I introduce the commands:
"Bootrec /Fixmb" (OK result)
"Bootrec /Fixboot" (OK result)
"Bootrec /RebuildBCD" (result no Windows facilities)When restarting the BIOS says:
"A Disk Read Occurred Error" + Strange symbols.
I repeat the commands and the result is the same.
Automatic repair does not work either.
Third parties programs do not find errors, repairing the MBR does not work, the hard drive and its partitions are accessible from XP.
Chkdsk does not give error.I have the following on this hard drive:
1-FAT32 Active Partition with boot manager.
2-NTFS Windows Vista.
3-FAT32 Windows 2003.
4-FAT32 Data.Then I start the Windows Seven repair disk console and I introduce the "BOOTSECT /NT52 C:" (not available in Windows Vista).
Now the BIOS boot the hard drive with boot.ini and Windows 2003 starts perfectly.
I enter the command again:
"Bootrec /Fixboot"
And the result is again that the hard drive is not accessible from the BIOS.
"A Disk Read Occurred Error" + Strange symbols.
Then I introduce the "BOOTSECT /NT60 C:" command: "
And now the Bootmgr menu to start Windows Vista reappears.
I enter the command again:
"Bootrec /Fixboot"
And the result is again that the hard drive is not accessible from the BIOS
"A Disk Read Occurred Error" + Strange symbols.My conclusions about the experiment to repair the start of Windows NT6 or higher is "impossible mission".
Strange errors also happened to me when trying to repair Windows Seven.
https://msfn.org/board/topic/184546-reov-boot-windows-lononghorn/?do=findcomment&comment=1242025
I will install Windows Vista again and I will enter the command again
"Bootrec /Fixboot"
To get out of doubt.In any case, the option to repair the start of Windows Vista has been from Seven's DVD "Bootsect /NT60 C:" and to exotate this this has been "Bootrec /Fixboot" from Vista's DVD.
0 -
On 3/13/2023 at 9:53 AM, NotHereToPlayGames said:
Correct, links are down for rebuild 7 due to space needed for rebuild 8 -- https://msfn.org/board/topic/184515-arcticfoxienotheretoplaygames-360chrome-v1351030-rebuild-8/
I will upload ALL versions one of these days to Internet Archive (including past v11, v12, and v13 builds).
Unsure when I will be able to do that.
Well, no problem. I have tried rebuild 8 and this works very well. I understand that all versions from Rebuild 7 are Ram-Friendly right?
I have tried it in Intel Atom Notebook 2010 Year with 1 Gib Ram and in Pentium IV with 2 Gib Ram, now this work very well.
At this time I do not find links to download any version. links are down?0 -
Has anyone achieved it, is there any method?
Experimentally I am trying to start Windows Vista 6.0.6000.16386 (Vista_RTM.061101-2205) Enterprise from NTLDR.
I have managed to get hast here.
Any tips to continue?
Windows Lonchorn/Vista, at least between versions 6.0.5048 and 6.0.5112 install bootmgr, but are also boot from ntldr version 2005 (Required*).
*Required NTLDR version 2005 (ntldr not OK version 2003 and not ok version 2008)
I am using this ntldr version and I have modified boot.ini on 6.0.6000
multi(0)disk(0)rdisk(0)partition(3)\Windows="Windows Vista" /NOEXECUTE=OPTIN /FASTDETECT /ACPI /HAL=HALMACPI.DLL /KERNEL=WINLOGON.EXEBut arriving at the point in the photo this gives the error "Load Needed Dlls for Hal"
I have tried to replace the original HAL 6.0.6000 with the HAL of 6,0,5112 but there is no difference.1 -
On 3/26/2023 at 2:28 PM, jaclaz said:
With all due respect, you seem like mixing all together a lot of things of which you have only a minimal understanding.
It is very unlikely (please read as "it won't work) that you will ever be able to start a later OS with the boot files of a previous one.
As well your attempt (if I get right what you attempted doing) to repair a Windows 7 boot using Vista files/tools is completely futile.
It is the first time I read about partitions disappearing when deleting the boot files, it makes very little sense, the NT 5 boot files (NTLDR, NTDETECT.COM and BOOT.INI) are completely offline/non accessed once the OS is booted. the NT6 file BOOTMGR is as well completely offline/not accessed BUT the \boot\BCD (which is actually a Registry hive) is instead online when the os is booted as it is mounted as HKLM\BCD00000000, so only deleting this latter file may (though I doubt it) create issues (like preventing the deletion or crashing) but I cannot see how it can modify anything connected to partitioning/filesytems.
Partitions DO NOT disappear, what may happen is that data is corrupted/changed in the MBR partition table, the Magic Bytes become invalid or - much more rare and the symptom is having RAW partitions - that some data in the PBR is corrupted/changed.
It is possible, since you are using (why) XP on a disk with partitions aligned to megabyte (2048 sectors) that it corrupts something, but it is unlikely, the only reports we have is about the XP disk manager that corrupts logical volumes inside extended, never primary partitions.
About this there are only two "conventions" about disk partitioning:
1) up to XP partitions start and end aligned to heads and cylinders (and since the most common HS geometry is 255/63 this means that first partition starts on 0/1/0 - i.e. 63 - and end on n/254/63)
2) starting from Vista partitions are aligned to whole megabytes (actually mebibytes) i.e. 2048 sectors x 512 bytes each = 1048576 bytes, the first partition starts at 0/32/33 - i.e. 2048)Clusters are related only to filesystems and their size have nothing to do with disk partitioning.
The NTFS default cluster size is 4096 bytes (no matter which OS, on any practical size of a volume), FAT32 cluster size affects (or is affected by) volume size, the FAT32 default cluster size of 4096 bytes cluster size applies only up to around 8GB, larger volumes will have larger cluster size.
If you want to troubleshoot the issue, you will need to learn how to make backups/copies of the MBR and of the PBR's and compare them in order to pinpoint what actually changes.
When you use "automagical" tools (easus/eassos/etc,) you don't know what they do, for all we know they might fix the actual issue but create another one.
About bootrec, you have to understand what it does:
https://ss64.com/nt/bootrec.html
Bootrec /fixboot writes new bootsector CODE, leaving the DATA in it untouched
Bootrec /fixMBR writes new MBR CODE, leaving the DATA in it untouchedso if the issue is with either the MBR or PBR DATA, they won't do anything.
The above link explains also how to use the bootrec /rebuildBCD (i.e. making a backup and then deleting the existing BCD in order to force the tool to completely rebuild a new BCD), still, given the mixing of files and operating systems, it is entirely possible that the installed OS is not detected or not detected properly, so often it is needed (though they both need some experience) to use BCDboot and/or BCDedit manually, in any case you must use the tools coming from the exact same OS you are trying to boot/repair.
A possible alternative (easier to use because it is GUI, but that still needs some knowledge of the way the BCD works) could be BOOTICE:
http://reboot.pro/files/file/592-bootice-v1332/
jaclaz
I have little knowledge about Windows NT6 start. This is evident.
I am now obliged to use an application that is no longer compatible with XP by imposition of the Government of Spain (Autofirma 1.8) to be able to send official documents to the country's administration.Before using any superior version of Windows 2003 on my personal computer, the first thing I want to know is how they start.
And not vice versa. Use these and these not start. Or what is worse, that the data of my main computer are erased.With all respect for who knows more, although some people have less knowledge can contribute a lot, if they work with collective intelligence. Well, all people have different points of view.
I am now doing tests in Windows Seven.
I have restored a backup copy of the starter boot.
I try to repair the installation from the Windows Seven console on another computer.
I have connected the hard disk by USB.
I follow the official steps, but the installation is not repaired.0 -
Some nuances about my previous comments.
The versions that start Windows with Bootmgr+NTLDR are the Shorthorn versions "Based Longhorn"
Since although the installer is Bootmgr these versions are really NTLDR.On the other hand, Longhorn Pre-Reset from 4000 to 4093 use a 32-bit installer but these are NTLDR and not Bootmgr implements.
Longhorn Post Reset, at least between versions 5048 and 5112 install bootmgr, but are also starting from NTLDR version 2005 (required*). These versions boot from both methods but these only install bootmgr.
The latest Longhorn version that can be installed in Fat32 is 5001. That is, it coincides with the last one that NTLDR has.
0 -
On 3/24/2023 at 4:06 PM, jaclaz said:
Boot.ini is ONLY a settings file, it tells NTLDR what to boot [1].
You are loading the NTLDR of your Shorthorn that (evidently) can boot the (previous) operating systems (2000 and XP), the inverse does not work, i..e. the 2K NTLDR can boot both NT4 and 2K but not XP, the XP NTLDR can boot XP and 2K (and possibly also NT4 but it would need to be tested) and so on.
Vista and later can ONLY boot via BOOTMGR.
You can add to your 2K or XP BOOT:INI an entry loading GRLDR (the grub4dos bootmanager) and have in its configuration file (menu.lst) a choice to chainload the BOOTMGR.
Other point: the "press any key to boot from CD" message comes from a file on the CD called bootfix.bin.
The idea is that you may (or may not) being booting a CD to install the windows for the very first time, i.e. on a blank/unpartitioned hard disk (intended use) OR you might be booting it on a machine with an already partitioned disk OR (common enough) you forgot the CD in and left boot priority unchanged and you booted to the CD by mistake on reboot after install, so, once the CD has been booted, the bootloader/bootsector of the CD runs bootfix.bin that checks the MBR being valid and only if it is, it shows the message. If the MBR is blank or invalid, the CD continues booting without need for a keypress.
Some more details here:
http://reboot.pro/index.php?showtopic=9540
jaclaz
[1] to be fair, though unrelated, non-arcpath entries in BOOT.INI are also parsed by BOOTMGR, I believe up to the one in Windows 8 or 8.1, surely up to 7.
It is possible that when the text did not appear "press a key to start the CD" the BIOS boot priority changed without realizing it, but when the message did appear I confirm that CD start priorities in the BIOS were correct. The Windows NT 5 (2000-XP-2003) installation CD was not able to start, when it was frozen for some reason, not being capable of detecting the hard drive modified by Longhorn/Shorthorn before being able to start the file installation load. To work again it was not effective to erase the hard drive and partition again.
The only solution was to convert the hard drive to GPT and covert it again to MBR.
The NT6.x DVD, yes did start correctly with this same hard drive before performing the conversion operation.I continue to do tests:
1-I have installed Windows Seven on the Notebook computer.
2-I have installed Shorthorn on the computer desktop.My purpose is to try to start Windows Seven with the Windows Longhorn boot, copying Shorthorn files into Windows Seven.
I still cannot comment conclusions, because in several tests the following has happened to me:
-As deleting the boot files from the active partition all partitions disappear. That is, with the hard drive connected as an external USB to Windows XP. I delete the "Boot" folder and all partitions disappear. I have performed more tests and also happens when Bootmgr, Ntldr, Boot.ini, etc. erase at the same time. This has not happened when one by one erase. I have copy and paste other folders that have not boot files and the problem has not happened to me.
I indicate that in certain circumstances Windows does not let these files erase, in others erases them without problems and in others the partitions disappear.Hard drive 4 partitions in Notebook computer:
1-Primary FAT32 Active partition with boot manager.
2-Primary NTFS Windows Seven.
3-Primary Fat32 Windows XP.
4-Primary FAT32 Data.From XP I install Windows seven in the second partition.
I confirm that now the number 1 partition begins in sector 2048 (I don't know if before).Then I extract the hard drive and connect it to the computer, it is the external USB and I started Windows XP. I erase some start files and partitions disappear.
This does not always happen. I don't know what depends.Then I have copy the original boot files of the Windows Seven and I have tried to repair the boot with the Windows Vista DVD.
1-I undo automatic recovery message Windows seven partition.
2-I execute the commands:
Bootrec /Fixboot
Bootrec /Fixmb
The result is that Windows Seven not starts.
Then I try to recover automatically, but the message repair Windows Seven now does not appear.
However, Windows Vista DVD says trying to repair.
The result is that not only does Windows Seven not start, but now the Windows Seven partition is in RAW and inaccessible. In addition the fourth partition appears inaccessible.
I try to recover the partitions with Easeus Partition Master but the program does not finish progress and does not find the correct partitions.
Then I again erase the Boot folder of the active partition and the partitions disappear again.
Then, after disappearing again, Easeus Partition Master does find and recover the correct partitions.
I am struck that this program also has the following MBR recovery options.
-2000/XP/2003
-Vista/2008
-7/8/10/2012
Is the Vista MBR and Windows Seven different?
I am investigating the initial sector by partitioning from the record administrator, it could be the following:
Sector 63 -> Windows NT 5.x -> Align hard drives with 63 sectors per track (512 bytes per cluster).
Sector 2048 -> Windows NT 6.0 -> Align hard drives with 4096 bytes by Cluster.
Sector 4096 -> Windows NT 6.1 and Superior -> Optimizes alignment in hard discs 4096 bytes by Cluster.The Eassos Disk Manager program allows you to choose the initial alignment when partitions are created and also allows partitions to the initial sector 63 since 2048 or 4096.
I do not extend anymore, this requires an integer post apart ...Ok, then I now try to recover the installation of Window Seven with Windows Seven DVD with the hard drive connected to the USB desktop.
I can't repair Windows Seven installation.
I execute:
-Auto recovery = It has not been completed.
-Console:
Bootrec /Fixboot
Bootrec /Fixmb
Bootrec /rebuildbcdBootsect /NT60 C:
No option manages to repair the boot.
With how easy it is to repair the NT 5.X boot it seems that NT 6.x boot resists me.
I can't repair Windows Seven boot.
0 -
Several strange things have happened to me that I cannot solve after trying to install the versions of Shorthorn that were not allowed to be installed from XP, because they said "the files cannot be found in the temporary path".
1-I can not repair the bootloader of the hard drive in XP format.
2-On boot the NT 5.x installation CD does not get past the "press any key to start the CD" screen with this hard drive.
3-Finally the boot CD does not start (it does not show the message press a key to start from the CD either).I tried to install Shorthorn Main Development 3801 from CD on another computer with a hard drive with 4 FAT32 primary partitions.
When I reboot the BIOS it does not find any operating system.
I check that in the boot partition there is the bootmgr, ntldr and boot.ini file but there is no Boot folder.I try to repair the boot by starting the Windows 2003 CD with the fixboot and fixmbr commands but the hard drive won't boot.
I copy ntldr, ntdetect.com and boot.ini from Windows XP to the boot partition and run fixboot and fixmbr again.
But the hard drive still won't boot.I delete all partitions from Windows XP and recreate 4 primary partitions in NTFS from Minitool Partition Winzard.
I reboot with the Windows 2003 installation CD in the CD drive and get the message "press any key to boot from CD".
I press a key but the installation CD does not start.
I try the Vista installation disk and it does start.
I delete the partitions again with Easeus Partition Master and the CD does not start either, then with Eassos DiskGenius and the CD does not start either, then with Macrorit Partition Expert and then the message "press a key to start from CD" no longer appears. from any NT 5. If NT 6 CDs are booted.
The problem only occurs with this SATA hard drive, after the operations performed.Edit:
I have managed to solve the problem by converting the disk to GPT and then converting it back to MBR with Acronis Disk Director. So I have installed Shorthorn 3801 on a single NTFS partition.
As a curiosity I comment that from this boot.ini I can start my other hard disk with w2000 and XP but from the boot.ini on the 2000/XP disk it does not start Shorthorn/Longhorn.
Is there a way to boot windows vista from a boot.ini?
It seems that this could be one way.
0 -
On 7/27/2008 at 12:26 AM, zzzz said:
Anyone knows how to make the active drive (the one that has the OS booted) become drive C?
Like before I had Vista on C and XP on D (if I'm using vista). When I booted to XP, the XP drive became C and Vista drive became D.
But now (after a new reinstallation), they stay the same regardless what OS I boot into. Why is that?
Caution only change the letter if the operating system previously used another letter. The letter change means that Windows does not find the paths of many files and does not work well.
The drive letter is determined within the operating system registry.
Part 1:
Change the drive letter from the operating system itself:
-Start+run+regedit
-HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices
-To change C: to D:
\DosDevices\C: rename to \DosDevices\Z:
\DosDevices\D: rename to \DosDevices\C:
\DosDevices\Z: rename to \DosDevices\D:
-Restart.Part 2:
Changing the drive of one operating system from another operating system.
Edit the registry remotely:
-Start+Run+regedit
-Select HKEY_LOCAL_MACHINE
-Go to menu File+Load subtree
-Find the SYSTEM file in the folder of the other operating system (on XP \WINDOWS\system32\config)
-Load SYSTEM and choose any name.
-Follow the steps indicated in part 1.
-Select the loaded subtree.
-Go to menu File+Download subtree.0 -
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.0 -
On 3/18/2023 at 7:57 PM, jaclaz said:
You can mean whatever you want by i386, but using the same language and conventions as other people usually helps in understanding.
Up to XP NTLDR is used
Starting from Vista BOOTMGR is used.
Your experiment with Shorthorn/Longhorn shows that in some versions both NTLDR and BOOTMGR are used, still the XP recovery console fixboot can only rewrite the PBR code to invoke NTLDR.
Since that works it means that - at least once installed - your Shorthorn/Longhorn boots via NTLDR (and not via BOOTMGR, unless there is another bootsector invoking BOOTMGR in BOOT.INI).
Checking the contents of BOOT.INI should be enough to verify (or confute) this.
A good idea would also be to make a copy of the bootsector (on FAT it is first sector, on NTFS it is the file $Boot or first 16 sectors of volume) before running the XP recovery console (when the OS is failing to boot) and compare it with a copy after having fixed it, there may be other changes besides the OS loader name.
I don't know which idea you are referring to, I don't recall having talked of Disk Manager in this thread.
However there is a known issue with the XP disk manager when used on a disk that has been partitioned with Vista and later.
As soon as you access it with Disk Manager AND change something (like making a primary partition active) then all logical volumes inside extended disappear.
The issue is talked about here:
http://reboot.pro/index.php?showtopic=9897
Only accessing the disk with Disk Manager shouldn't create issues, and in any case the issues are only related to logical volumes inside extended (primaries are unaffected), so what you report seems like news, and it is likely something peculiar of Shorthorn/Longhorn.
jaclaz
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.
Greetings1 -
On 3/16/2023 at 3:27 PM, jaclaz said:
No windows version use I386 to boot, I386 is a folder where installation files are for some windows versions.
I believe you mean that Longhorn requires NTFS filesystem for the "system" (what MS would call boot) partition.
Since NT 3.1 Windows has been designed to work with two partitions, one (that everyone calls boot, but MS calls system) that contains the boot files and is active in the MBR table and one (that everyone calls System, but MS calls boot) containing Operating system files:
http://www.multibooters.co.uk/system.html
The requirement for this second partition being NTFS came with Vista (but very likely Longhorn already has it), the first one can be anything, including a FAT12 bootdisk.
It really depends on how you install whether you have a single partition (that then needs to be NTFS) or two (in which case only the second needs to be NTFS).
You will likely have different drive lettering if you are using one or two partitions, depending on the specific way you install:
http://www.multibooters.co.uk/quirks.html#c_drive
Bootsect.exe will work on FAT12/16/32 and NTFS, the third party utilities I mentioned probably only on FAT12/16/32 (but has to be checked).
Up to XP Windows boots via NTLDR (and NTDETECT.COM)
Vista boots via BOOTMGR AND NOT via NTLDR.
Longhorn depends - I believe - on specific version.
jaclaz
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 FAT32but 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.0 -
On 3/15/2023 at 2:04 PM, jaclaz said:
In MBR style disks the booting sequence is either:
BIOS->MBR->PBR of active (primary) partitiion-> NTLDR (and NTDETECT.COM)->BOOT.INI->choice of OS
or
BIOS->MBR->PBR of active (primary) partitiion-> BOOTMGR ->\BOOT\BCD->choice of OS
The "fixboot" command in XP recovery console simply re-writes the PBR (bootsector) code with the one designed to invoke NTLDR.
The equivalent in a "full" system (Vista or later) is bootsect (with the /NT52 switch), NO idea if there is one in Longhorn nor which type of code it writes, some details on various versions:
https://msfn.org/board/topic/171749-bootsectexe-various-versions-compared/
Since longhorn/shorthorn is midway between XP and Vista it is possible that the version you installed (that clearly needs to use NTLDR as it is fixed by the XP recovery console) *somehow* writes the bootsector invoking BOOTMGR and then Vista does not recognize the install (basically because there is no BOOTMGR not \boot\BCD.
Third party, both bootpart.exe (by Gilles Vollant) and MBRFIX.exe (by Kaare Smith) should do (create a bootsector invoking NTLDR[1]), see also:
http://reboot.pro/index.php?showtopic=5251
Something that you can try (as it costs nothing) is to make a copy of NTLDR and save it as BOOTMGR along NTLDR, very likely the bootsector loading code is the same for both.
As a matter of fact at least in some versions of the boot code - on NTFS - it is possible to change the pointer to the string with the name of the loader as both strings NTLDR and BOOOTMGR are present (on FAT/FAT32 you need to change the actual name).
Of course IF my guess is correct, the "XP" code invokes NTLDR and has the message "NTLDR is missing" the "Vista" one invokes BOOTMGR and has the message "BOOTMGR is missing", your longhorn code could be invoking BOOTMGR but still have the "NTLDR is missing message", but it may well be any other type of problem.
jaclaz
[1] though it has to be checked if it is possible to do that on a NTFS volume, very likely both tools can only deal with FAT (16 or 32) volumes, so they would only work if you use a (small) Boot partition (what Microsoft would call System) and bootsect.exe remains the only simple tool to fix the issue
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.0 -
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?0 -
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 Tools0
Latest Version of Software Running on XP
in Windows XP
Posted · Edited by Cixert
I am experimenting.
It seems that the offline version AVG Antivirus Free 18.8 does not exist.
No page with old version software has it, these jump from version 17 to 20.
https://support.avg.com/answers?id=9060N0000005KegQAE