Os Loader V4.01

0 views

Skip to first unread message

Octavis Uberstine

unread,

Aug 3, 2024, 4:48:45 PM8/3/24

to checrosenet

I am unable to boot into NT, as I get as far as the "NTDETECT" and "OS
Loader" screen and I get the following error message:Windows NT could not start because the following file is missing
\system32\ntoskrnl.exe
please re-install a copy of the above fileThat however is incorrect, as my NT4.01/SP-6 files are all intact. I
believe that the OS Loader is pointing to the wrong partition. How do I
redirect the OS Loader to the correct partition and files?Thanks.

You need to edit the ARC path in C:\boot.ini to point at your current boot
partition.Best regardsBjorn
--
Bjorn Landemoo - bj...@landemoo.com -
Microsoft MVP - Windows NTGerald Jeremiah wrote:

>Hi,
>
>I am unable to boot into NT, as I get as far as the "NTDETECT" and "OS
>Loader" screen and I get the following error message:
>
>Windows NT could not start because the following file is missing
>\system32\ntoskrnl.exe
>please re-install a copy of the above file
>
>That however is incorrect, as my NT4.01/SP-6 files are all intact. I
>believe that the OS Loader is pointing to the wrong partition. How do I
>redirect the OS Loader to the correct partition and files?
>

That's my boot.ini above. Since I multi boot with 3 OSers, how can I
obtain the information as to the location of the disk, partitions, etc.?Somehow, I think that PQ Magic changed the location of my drives or
boot.ini when I accessed the utility after installing a new EIDE HDD.Initially, I only had two SCSI drives installed. Presently, I have two
SCSI drives and one EIDE. The boot drive is still the SCSI.What would a typical NT boot loader look like?Thanks

I am using the ST-Link utility, v4.0.0. I created a custom external loader in IAR for ARM using one of the example projects. After I build the loader in IAR I copy the .out file to ST Link's external loader folder and give it an STLDR extension. However when I go to load the file through ST Link, the Device name is blank, the Device Type is 'Unknown Device, the Start address is 0 and the Device Size is 0. I know that this information comes from the Dev_Inf file but since I just modified an existing project, I think this is all setup correctly. I have built this both in IAR v7.3 and v7.8. Any guidance would be appreciated.

You probably want to start by looking a the file with an ELF inspection tool to see what data sections and symbols are being exported. In Keil there is FromELF, not sure what the 'objdump' equivalent is in IAR

I have upgraded to v4.1 and I am now using the map files to compare the one of the example projects with mine. However, I did copy the .out file from the example I am examining to the ST Link External Loader folder and it too is showing up with an empty Device name, unknown device type, etc. I did not re-build the example - I just took the .out file as-is, copied it and gave it the .stldr extension.

IAR has a ELF dump utility that I used to dump the binaries. The main thing that stood out to me is that the known good loader had two program headers in it while my custom loader does not. I noticed that other good loaders also have that (both dumps are attached to this post).

I think I found the issue. I re-built my loader in IAR v7.3 and it was recognized by ST-Link. I did the same with one of the examples and that worked as well. (Originally I built my loader in IAR v7.8). Is there something that could be tweaked to make the build work with IAR v7.8?

Thanks Clive. I can't provide my specific code but I can provide the ST example code built in v7.3 IAR and built in v7.8 (example code built in v7.8 had the same behavior as mine). Which files would be the most helpful? A copy of the .out and .map for each?

I am facing a weird error when I installed Bootstrap. The error is below. I tried uninstalling less-loader and installing [email protected], because I saw it online, but it did nothing. I am unsure what to do at this step.

You will have to wait until Vue CLI V5 (will use Webpack 5) is released (currently in Beta) in order to use sass-loader v12.Alternatively, you can update to Webpack 5, but be sure to read the CHANGELOG.

When using Webpack version 4, the default in Vue CLI 4. You need to make sure your loaders are compatible with it. Otherwise you will get errors about conflicting peer dependencies. In this case you can use an older version of the loader that is still compatible with Webpack 4.

NPM downloads dependency packages to modules inside the module if they are in a different version than one in your package.json, but sometimes it downloads the latest version or dependent package (I don't know why) into a module...

For example, you can have sass-loader: 2.X in your package.json, and a module XXXX which also has sass-loader: * in its dependency packages (you can check that in package.json inside that XXXX module).

Make the change you want in ino, then save (maybe with a new name).
Then use teensy loader to load that file. Arduino 1.8 plus i think 1.57 add on work(the wiki have am instruction about how to load using 1.8. Arduino ino version 2 have many problems loading autosteer correctly to teensy.

If you renamed the autosteer file, then you still must save it in the same folder where the other connected files are (like zEthernet.ino)
All the needed ino files then open together with the autosteer file.

Bus Pirate firmware v4+ requires a bootloader upgrade. The upgrade frees space for more features, eliminates verify errors in the last page of memory, and fixes the bootloader speed limitation on some PICs. The new bootloader is available to everyone through an upgrader firmware that is loaded using the existing bootloader.

A v4 bootloader for Bus Pirate v1a is included in firmware downloads, but you'll need to program it with a PIC programmer, no upgrade utility has been made. No further support is planned for Bus Pirate v0a or v2a hardware. Upgrade instructions follow.

What we're going to do is use the existing v2 bootloader and P24QP.exe application (or Python script) to upload a bootloader upgrader. The upgrader will erase and reprogram the correct parts of the PIC flash memory with the new bootloader. After the new bootloader is programmed, we'll erase the installer and old bootloader by uploading a v4 Bus Pirate firmware.

The Python utility erases the entire chip, including the 'configuration words' that determine how the pic behaves on start-up. The v4 firmware does not contain replacement configuration words, so the Bus Pirate won't start from the correct clock after programming a v4 firmware to a v2 bootloader with p24qp.py. Only Upload v2 firmware or BPv3-v2blupdaterVa3-v4.1.hex with P24QP.PY.

Despite this warning, some will still be tempted - don't do it, it's the only significant source of upgrade failures. Read all the steps here first, before you upgrade. Heed the warnings in the firmware archives - please don't try to upload v4 firmware to a Bus Pirate with a v2 bootloader.

Upload ' BPv3-v2blupdaterva3-v4.1.hex' to the PIC with the existing v2 bootloader. Use your normal upgrade procedure for the v2 bootloader to load the upgrade HEX into the PIC. V2 bootloader instructions for: Windows, GNU/Linux, OSX.

Pirate-Loader console utility: The ds30 Loader GUI requires .NET or Mono, and doesn't work for everyone on GNU/Linux or MaxOSX. Pirate-Loader is a simple command line utility for firmware upgrades on all platforms that doesn't need .NET or Mono.

Connect with a terminal and print the information menu (i). Firmware v4+ reports the bootloader version. Bootloaders installed with the upgrade utility will report v4.1. Bootloaders installed from the v4.1 firmware download (using a PIC programmer) will report v4.2. There's no functional difference, it's just a way to better handle support requests.

To upgrade the bootloader you have first deconnect the buspirate, bridge the two pins PGC and PGD, and re-connect the buspirate again. Then you're ready to load the upgrader (find the id of your buspirate by tabbing after usbserial):

I also use a FP4 with locked bootloader and it never worked for me. Iod blocker is set to not block anything for the app and SafetyNet is activated. It seems to be somehow related to the FP4, at least the app is marked as compatible in the list (for older Iod version) and i did not find much about it searching the forums some time ago.

I've just bought a new tp-link archer MR200 V4 the only problem it has is that it's from an ISP so it runs a custom firmware. I've seen several posts from other users in this subforum but most of them without a reliable solution (remember that mine is V4 not V1).

I know a guy compiled a version for my router ( ) by @Lochnair but i cant use it because my router uses a custom bootloader (Orange/Amena Espaa) and i cant extract it. So my only solution for now is a dump, I've found one for the v1 version in this forum but the link is down TP-Link MR200 firmware update - #79 by jmpcarceles

Im running a custom firmware from my ISP but i want the official TPLink firmware. The problem is that as far as i know i'll need the custom bootloader that my ISP uses to be able to switch to the normal firmware.

get the bootloader from your ISP update firmware file. download the full firmware and extract the bootloader the same way as you would with the official TP-Link firmware. If you have problem extracting it, just send the link to download and i will help with the extraction.

I probably should make a gui program in windows that would be able to extract the bootloader, router firmware, and modem firmware from this TP-Link model. There are many wanting help regarding bootloader extractions.

I found out from past members results that using the official tp-link bootloader for amena/orange (probably others too) will cause problem for tftp. Their LAN would not come up from boot and so it wont be able to accept firmware upgrades from tftp. using the original bootloader from their ISP will fix it. I only have the official version of MR200V1 so I am only able to make this conclusion from other members results.