Windows Longhorn Pre-Reset

13»

Comments

  • edited March 7

    I was curious enough to install 3718 on my ThinkPad T60. Things were going great until I attempted to install the win2k M$ HDA bus driver and the one for the Mobility Radeon X1300 (an XP-only driver from 2009; I was too lazy to look for my copy of the win2k version). Then it booted up into a blank screen!

    When it did boot up properly, it slightly edged out a clean 2003R2 SP2 install in terms of boot speed which is impressive for the hardware.

  • @Fa397bio said:

    @Andre Morales said:
    I have seen that these betas work with very old versions of VMware Tools (like 4.5.3 to 5.5.9). Its functions inside the machine give good results.

    And Where do i get these VERY OLD VERSIONS OF VMWARE TOOLS?

    Use this page to download: https://www.thecollectionbook.info/information/downloads/

  • @Fa397bio said:

    @Andre Morales said:
    I have seen that these betas work with very old versions of VMware Tools (like 4.5.3 to 5.5.9). Its functions inside the machine give good results.

    And Where do i get these VERY OLD VERSIONS OF VMWARE TOOLS?

    Look here: https://thecollectionbook.info/information/downloads/

  • edited May 24

    @WildSkinnyWhiteBoi said:
    wheres, 3706, 3713, 4001, 4084 and 4088.

    WWPC's collection is not as complete as BA FTP.

    @WildSkinnyWhiteBoi said:
    I'm using longhorn 4093 on pentium iii pc, shit.

    What do you mean by "shit"? Do you mean that the experience is bad?

    @WildSkinnyWhiteBoi said:
    and Longhorn 5112 May Work on pentium iii pc with 512 mb of ram.

    No, you need at least 1GB of RAM to run 5112 and above stable. 512MB is the minimum for 5112-6000.

  • edited June 14

    @Jorge Mendez said:
    Even if not leaked yet, please add the following builds:
    3551, 3663, 3713, 3790 and 4001

    and also, builds 4015 and 4039 are NOT bootable. I want them to be bootable

    ...you surely don't know the meaning of "leaked" do you?

    @TheCreepy234 said:
    this is what i have the F**king BSoD

    Please provide information; error code, build, VM software and specs of your VM.

  • Can anyone tell me how to fix this error when I try to install Windows Longhorn build 4051 on actual hardware?

    The file WinSetup.dll is not loaded or corrupt. Setup cannot continue.

  • @BF10 said:

    @unscchief1178 said:

    @TheCreepy234 said:
    this is what i have the F**king BSoD

    i get a bsod if i try to install

    Set the hard drive to IDE, set back your BIOS date, and use older compatibility if running VMWare.

    The reasons:
    1)Because Windows Longhorn is based out of XP,the installers don't like SCSI/SATA.
    2)If you install Windows Longhorn without setting the BIOS date,the OS will send you to the logon screen.
    3)I don't know why older compatibility on VMware is needed,so I have nothing to say about it.

  • @Missileboi said:
    Can anyone tell me how to fix this error when I try to install Windows Longhorn build 4051 on actual hardware?

    The file WinSetup.dll is not loaded or corrupt. Setup cannot continue.

    Are you using the chk version?

  • @Windows 2000 said:

    @Missileboi said:
    Can anyone tell me how to fix this error when I try to install Windows Longhorn build 4051 on actual hardware?

    The file WinSetup.dll is not loaded or corrupt. Setup cannot continue.

    Are you using the chk version?

    I think no,but I will re-download it.

  • Do NOT use the chk version. It is broken.

  • Can anyone tell me how to fix this error when I try to install Windows Longhorn build 4074 on actual hardware?

    NTDETECT failed

  • @Windows 2000 said:
    Do NOT use the chk version. It is broken.

    And then why does WinWorld have a chk version?

  • Someone DID get the chk version working, but I can’t remember how. The only difference is that the chk versions are debug builds.

  • @Missileboi said:

    @BF10 said:

    @unscchief1178 said:

    @TheCreepy234 said:
    this is what i have the F**king BSoD

    i get a bsod if i try to install

    Set the hard drive to IDE, set back your BIOS date, and use older compatibility if running VMWare.

    The reasons:
    1)Because Windows Longhorn is based out of XP,the installers don't like SCSI/SATA.
    2)If you install Windows Longhorn without setting the BIOS date,the OS will send you to the logon screen.
    3)I don't know why older compatibility on VMware is needed,so I have nothing to say about it.

    You need older compatibility to make it easier to install the builds, and it can also help even get DCE and Aero effects on some builds.

    @robobox said:
    Someone DID get the chk version working, but I can’t remember how. The only difference is that the chk versions are debug builds.

    AFAIK someone on the BetaArchive Discord managed to get the x64 build to install, but it requires editing setup files and requires an AMD processor.

Sign In or Register to comment.