WinNTSetup v5.4.1

[ibay770]

I have no choice 🤣

[ibay770]

On 3/6/2022 at 5:12 PM, alacran said:

JFYI

My Mini-10_es-MX.vhd boots very fine now. (Made using Win10_2004_Spanish(Mexico)_x64.iso)

By the way there is a typo in the file name it says: Lanugages.txt not Languages.txt

Any way I edited it to keep all es-ES and es-MX, and saved with both names, your program will use the one it has coded, during you fix the typo.

For use in es-MX version, I did same thing in my modded version of SySWoW.txt that was used in Mini-10-US.vhd to fix LibreOfficePortable issue, and also try to cover other possible cases like that.

Also edited System32-DLL.txt, commenting the following lines:

; \Windows\System32\KBDLA.DLL   >>>   Spanish Latin American KB

; \Windows\System32\KBDSP.DLL   >>>   Spanish KB

; \Windows\System32\SensApi.dll   >>>   Requided to boot notepad++   now it boots and works fine, but fails when trying to save as....

I found Paint can't also save as... but I had same issue before in a wimb's project aand I know the cure for that:

; \Windows\System32\shellstyle.dll   >>>   This is used by Paint to save as...., this very possible will also fix same issue in notepad++ (pending to test, will report back).

 

Adding WlanMM.dll, let me see the available Routers now, but if selecting one, the usuall next dialalog to Connect and type the Password is not shown. Something else is still necessary.

alacran

 

got another link to syswow.txt?

link is down.

[click-click]

I have an updated W7 vhd that I boot loacally and I want to now use it in a VM (VBox). Since the BCD for booting was loacated outside of the vhd, I used Winntsetup to redo the BCD as shown below. The problem is, when I use the vhd in a VM, it starts to boot, but BSODs with 7b. When I try safe mode, it also abends. The last entry I see on the console before the BSOD is Classpnp.sys which is a storage class driver. So I assume I have a disk  or controller driver installed in the vhd that doesn't work in a VM which may be causing the crash.

@JFX or anyone else that might know how to resolve this, or something to try, please let me know.

Edited 57 minutes ago by click-click

[NotHereToPlayGames]

Try this  --  https://sourceforge.net/projects/vmma/

[NotHereToPlayGames]

Or this  --  https://backupchain.com/i/vhd-to-vhdx-vmdk-vdi-physical-disk

[click-click]

I don't think any of these apps will install  drivers for a VM when converting (I've already tried some others). Since I already have a bootable working VHD there is no need for me convert unless there are apps that actually redo the storage drivers to work in a VM which I doubt. Finding the non-compatible driver(s) in the VHD is the problem.

 

6 hours ago, click-click said:

 

 

Edited 3 hours ago by click-click

[NotHereToPlayGames]

This sounds "too easy" of a fix, but I'll go ahead and say it out loud  --  have you tried booting into "safe mode"?

[click-click]

Please read my OP entirely. Been there, done that. So what's the fix?  

Edited 53 minutes ago by click-click

[NotHereToPlayGames]

Did originally.  Forgot as time went on, lol.

If it were me, my next step would be to uninstall your current version of VirtualBox (which I have to assume is "new") and drop down to the 5.x branch.  I'd have to research further, but you want a version that PRE-DATES hardware capabilities like "TPM".

Just a hunch...

[NotHereToPlayGames]

I've never done what you are attempting, I admit, so I am only going by "educated guess".

We use Acronis at work for the task you are attempting.

But it's also one of those things we only need to do once every 18 months or so.

We all forget the process and have to reinvent the wheel every time.