Can't even get Longhorn build 4042 and others setup to start

[Valerio]

Hi! I'm trying to install Longhorn build 4042 in VMware Workstation 7.0.0 and I am using the usual configuration for my Longhorn virtual machines that has always worked, that includes using IDE drives and configuring the VM as Windows XP and such, but as soon as I boot the virtual machine the boot screen just ends up looping, I can't even get to the installation screen. I just see the orange progress bar moving infinitely. When I try to install build 4066 instead setup hangs at "Setup is starting Windows.", meanwhile Longhorn build 5048 boots just fine. That is weird since I've always managed to boot every Longhorn build in VMware without any issues. Now it looks like I am having trouble installing pre-reset builds only. Only thing that's different now is that I am using a new laptop I recently bought which features a Core i3 6006U (Skylake). Could that be the issue? Is there any particular setting I should change? Please don't just tell me to upgrade my VMware version (unless that's absolutely necessary, but I don't think so since this problem seems to affect pre-reset builds only, probably it's just some setting that needs to be changed. I'd like to stick with version 7 since it seems to be the easiest way to run DWM). Thanks in advance! Oh, and my host system is Windows 7 x64.

[BF10]

Did you use VMware 5.5 or 6.0 compatibility with these builds? Sometimes not setting VMware compatibility can cause issues with these builds.

[Valerio]

I tried but it didn't work at all

[ATeamInc]

The infinite orange progress bar? Hey, I've just faced this exact same problem with 4042 (And this happened TODAY). The solution? I used the Longhorn Packet 1.21 CD. Really simple, seems to do the job pretty well.

[Valerio]

I even upgraded to Windows 10 x64 now and VMware Workstation 12, but the problem still persists... And yes I know about Longhorn Packet, but I'd like to fix this issue without any third party software... just what is causing this boot loop?

[Zv45Beta]

Not sure this may help, but you can try disabling VT-x and VT-d... is the drive set to IDE on the pre-reset build VM?

[Valerio]

I think it's already disabled because the checkbox about VT-x is unchecked... well I'm going to go for Longhorn Packet for now, but still this is so annoying. And yes the drive is IDE, both CD-ROM and HDD.

[Zv45Beta]

I think it's already disabled because the checkbox about VT-x is unchecked... well I'm going to go for Longhorn Packet for now, but still this is so annoying. And yes the drive is IDE, both CD-ROM and HDD.

So true, last pre-reset builds are such a pain to set up, unfortunately...

[Valerio]

I got Longhorn Packet to boot up correctly and I'm now installing build 4042, hope everything goes fine
I miss the old days when setting up every Longhorn build was easy peasy in my good old laptop and VMware 6.0... I'll let you all know when I'm finished installing. Crossing my fingers.

[Zv45Beta]

I got Longhorn Packet to boot up correctly and I'm now installing build 4042, hope everything goes fine
I miss the old days when setting up every Longhorn build was easy peasy in my good old laptop and VMware 6.0... I'll let you all know when I'm finished installing. Crossing my fingers.

That's why I keep a Core 2 Duo desktop with XP installed ready for something like that

[Valerio]

Yeah, good old Core 2 Duo PCs will always come handy! Anyway Longhorn Packet worked and I have now installed build 4042 successfully. I would like to thank everybody who replied to this topic and helped me. I'd like to hear though if there are any other solutions apart from using Longhorn Packet . I'm curious now to see how will I install build 4066 which uses old i386 setup... I don't think I can use Longhorn Packet for that one

[XaddaGamer]

I started setup from build 4039 and installed it. Upgrade to this build not worked me on VMware and shows a error lssas.exe. I just taked a clean install and work on it.

[Caveria]

Start setup from Windows 2000 or XP and run it. Clean installation choose, because upgrading is not working for that and showing us lssas.exe error by result reinstall this build with properly doing.