Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 



Sign in to follow this  
diamant

Install WinXP on Acer Aspire 3810T-354G32N, always bluescreen or black

Recommended Posts

diamant    0

I try to install WinXP on a Notebook

"Acer Aspire 3810T-354G32N".

 

By trying this I get only trouble :blushing: .

Problem 1: The Acer doesn't have a floppy- or CD-ROM-drive, which makes booting difficulty. I can only boot from USB-stick.

 

I can prepare USB-Sticks with Rufus or WinSetupfromUSB to be bootable.

Problem 2: If I use Rufus, so the USB-Stick will not be bootable on the Acer.

 

But I can "solve" problem2 by using WinSetupFromUSB (I tried several Versions, 1.0beta7 and 1.4).

What I already did with WinSetupFromUSB:

- Made a USB-Stick bootable with FAT32 file format

- created a USB-Stick with WinXP-install-files; thereby the files were copied directly from a WinXP-install-CD, not from an ISO-file.

 

Then it is principially possible to boot from this USB-Stick; I get first this screen http://www.winsetupfromusb.com/wp-content/uploads/2013/09/Ashampoo_Snap_2014.01.20_17h30m44s_001_QEMU.jpg and can select

the WinXP Setup. The setup at the first starts fine, but after loading FAT file system I get

- either a bluescreen with the 0x0000007B error (if I created the USB-Stick with WinSetupFromUSB1.0beta7)

- or a blackscreen with blinking cursor in the top left of the screen.

 

At http://www.winsetupfromusb.com/faq/ and http://forum.notebookreview.com/acer/586065-xp-aspire-3810t.html there are described some workarounds. I have tried some of them:

 

1.) I have already tried a modified ntdetect.com Ntdetect.7z, with no difference.

2.) I changed the BIOS setting "SATA MODE" from "AHCI Mode" tho "IDE Mode" and back, with no difference.

3.) I tried to select "Auto-detect and use F6 SATA/RAID/SCSI Driver" like described in http://www.winsetupfromusb.com/wp-content/uploads/2013/09, with no difference.

4.) I installed nLite on my (working) PC and tried to add following driver AHCI_Intel_8.8.0.1009_XPx86XPx64_A.zip, which also can be downloaded from Acer's website: http://global-download.acer.com/GDFiles/Driver/AHCI/AHCI_Intel_8.8.0.1009_XPx86XPx64_A.zip?acerid=633773721411807534&Step1=Notebook&Step2=Aspire&Step3=Aspire%203810T&OS=X01&LC=en&BC=Acer&SC=PA_6.

But even 4.) had no effect :angrym: ! I get still the blue- or black-screen described above.

 

Maybe I did something wrong? I think I have added the driver not properly into nLite. Could it have something to do with the fact that I would need "text mode drivers" (or similarly)?

 

PS: I had to unpack the nLite ISO- file before creating the bootable USB-Stick with WinSetupFromUSB.

PPS: Here is the *.ini-file created from nLite LETZTE SESSION.INI.

Share this post


Link to post
Share on other sites

jaclaz    940

 

2.) I changed the BIOS setting "SATA MODE" from "AHCI Mode" tho "IDE Mode" and back, with no difference.

 

That is very queer.

The 0x0000007b is "inaccessible boot device" and it is normally caused by a missing driver for the hard disk, but in IDE mode it should not happen, at least, not even on pesky BIOSes, when the modified NTDETECT.COM is used. :unsure:

 

Try again integrating the SATA drivers, after having read this:

http://www.msfn.org/board/topic/107504-integration-of-intels-sata-ahci-and-raid-drivers/

http://www.win-raid.com/t22f23-Integration-of-Intels-AHCI-RAID-drivers-into-a-Windows-XP-W-k-W-k-CD.html

 

Would it be possible that for any reason you are providing a set of "wrong" drivers? 

(or that they were modified in a incompatible way by Acer or something like that)

 

Alternatively, you can try one of the "alternate" ways:

http://www.msfn.org/board/forum/157-install-windows-from-usb/

if you can make a 7 PE of some kind, or even tty the good ol' USB_MultiBoot.cmd:

http://www.msfn.org/board/topic/111406-how-to-install-xp-from-usb/

 

Or try with RMPREPUSB in a more "manual" way:

http://www.rmprepusb.com/tutorials/install-xp-from-an-iso

 

jaclaz

Share this post


Link to post
Share on other sites
Ponch    4
PS: I had to unpack the nLite ISO- file before creating the bootable USB-Stick with WinSetupFromUSB.

You don't have to. The ISO file is a packing of the working folder, so all those files did not need packing at 1st. Also you can skip "Make ISO" if you don't need the ISO, that 'll make you gain 1 minutes.

Any doubt the HDD itself? (What's the reason you reinstall at 1st?)

Share this post


Link to post
Share on other sites
diamant    0

The 0x0000007b is "inaccessible boot device" and it is normally caused by a missing driver for the hard disk, but in IDE mode it should not happen, at least, not even on pesky BIOSes, when the modified NTDETECT.COM is used. :unsure:

Here ist the whole bluescreen when using WinSetupFromUSB_1-0-beta7:

post-254155-0-44884000-1417176915_thumb.

 

Would it be possible that for any reason you are providing a set of "wrong" drivers?

(or that they were modified in a incompatible way by Acer or something like that)

 

I downloaded them directly from Acer, finding the drivers by typing the serial number of the 3810T.

The guy at the link I've already posted http://forum.notebookreview.com/acer/586065-xp-aspire-3810t.html used obviously the same drivers?! :unsure:

I read some of the links you posted; I think maybe there's somewhere the solution for my problem. Problem is that it's impossible(?) to find out the exact information about chipset from that Acer Aspire 3810T-354G32N because system analyzing tools won't run in MS-DOS.

 

Any doubt the HDD itself? (What's the reason you reinstall at 1st?)

Of course I can not exclude that de HDD itself is (physically) damaged in any way.

The reason for reinstalling ist/was malware; the previous OS (WinVista) was heavily infected. I recommended the user to use WinXP; he has no WinVista CD or USB-Stick.

But I have another new information:

I have accomplished it to install MS-DOS on the Acer! :yes:

Here the instructions (i.e. my way to proceed this):

1.) Create a bootbable USB-stick with MS-DOS. You can use any tool for that; I recommend HPUSBFW_v2.2.3.exe.

2.) Download Ranish Partition Manager v2.40 and unpack it onto the USB-Stick. You'll find a DOS-program part.exe.

4.) Copy the DOS-files format.com, xcopy.exe, xcopy32.exe, xcopy32.mod on USB-Stick.

3.) Boot the Acer from USB-stick.

4.) Start part. In the following screen (from Ranish Partition Manager) select Harddisk 2 (the internal HDD), delete all partitions on it, set the MBR to "Standard IPL", create a new partition, format it (it can be done in Ranish Partition Manager), and (important!) set the Boot flag for the new partition. Save the new settings with F2.

Exit now Ranish partition manager.

5.) Start format D:/Q/S. Here is D: the internal HDD, Q means "quick format", S is for installing MS-DOS files (from USB-Stick, which should be actually C:) to D:.

6.) Unplug the USB-Stick.

7.) Restart the Acer and set boot settings in BIOS to HDD. It shoult now boot MS-DOS from the internal HDD, which is now C:.

I think this could be a possible basis for installing WinXP directly from the internal HDD?! I could copy all WinXP install files to the internal HDD, boot from HDD and try to start the setup directly from it.

If this fails, so I can say that the problem is not the fact that I try to install from USB?!

Edited by diamant

Share this post


Link to post
Share on other sites
jaclaz    940

I think this could be a possible basis for installing WinXP directly from the internal HDD?! I could copy all WinXP install files to the internal HDD, boot from HDD and try to start the setup directly from it.

If this fails, so I can say that the problem is not the fact that I try to install from USB?!

 

Yep :thumbup, of course "been there done that" ;) here is the actual "howto":

http://www.911cd.net/forums//index.php?showtopic=16713

JFYI that thread more or less originated, see also this:

http://www.msfn.org/board/topic/81788-installing-unattended-from-a-usb-thumb-drive/?p=563654

the "whole" section:

http://www.msfn.org/board/forum/157-install-windows-from-usb/

 

The current version of WinsetupFromUSB is however 1.4:

http://www.msfn.org/board/topic/120444-how-to-install-windows-from-usb-winsetupfromusb-with-gui/

http://www.winsetupfromusb.com/downloads/

 

and hopefully it works "better" than WinSetupFromUSB_1-0-beta7 (and BTW also includes the DPMS drivers, so, normally you should not need to integrate your drivers).

 

The very queer thing as said is that you have the same result with the BIOS set to "IDE compatibility mode" (and if this is the case *any* "normal", "untouched" XP source should give not the 0x0000007b error - if not because of the NTDETECT.COM) :unsure: or, if you prefer, there must be something not related to the SATA driver integration if the result is the same 0x0000007b with the integrated source or with the "plain" one.

 

jaclaz

Edited by jaclaz

Share this post


Link to post
Share on other sites
diamant    0

The additional problem which I had was the fact, that the Acer was not able to boot from its internal HDD.

I could start  'format D: /Q/S'  from the USB-Stick C:, that means on D: there were the 3 needed DOS-files io.sys, msdos.sys, command.com. But after that the internal HDD was not able to boot (with unplugged USB Stick). I always got  

"no bootable device - insert boot disk and press any key".

 

So it was necessary to use a program like Ranish partition manager:

- to set the MBR (master boot record) of the internal HDD from somewhat like "undefined" to "Standard IPL"

- to set the Boot flag to "active",

That was not possible with fdisk and/or format.

Only after that executing  'format D: /Q/S'  showed an effect.

 

The current version of WinsetupFromUSB is however 1.4:

I tried also this newer version. By using it I got not the described bluescreen, but instead a blackscreen with blinking cursor in the left. It seemed that meanwhile was loaded some setup data(?) in background, but I waited for ca. 30 minutes, and nothing happened.

That means: The difference between v.1.0beta7 and 1.4 is only the colour of the screen when stopping WinXP setup... :w00t:

Or maybe I simply had to wait a little bit longer than 30 minutes...? :huh:

 

The very queer thing as said is that you have the same result with the BIOS set to "IDE compatibility mode" (and if this is the case *any* "normal", "untouched" XP source should give not the 0x0000007b error - if not because of the NTDETECT.COM) :unsure: or, if you prefer, there must be something not related to the SATA driver integration if the result is the same 0x0000007b with the integrated source or with the "plain" one.

The user littlebigman on http://forum.notebookreview.com/acer/586065-xp-aspire-3810t.html had also set the BIOS setting to "IDE compatibility mode", with also no effect. Maybe the BIOS is broken by design. User littlebigman wrote furthermore that he integrated the said Acer's AHCI Intel SATA AHCI Driver (8.8.0.1009) with nLite[#], and had to set in BIOS the "IDE compatibility mode".

[#]No idea how he integrated driver; maybe I integrated them wrong?!

 

Tomorrow I can make a first try to install WinXP from the internal HDD by the method to start  winnt.exe  directly from I386 folder (on internal HDD).

 

When change from AHCI to IDE, you can install XP?

Until now: No, it has no effect. See also (as said) the link http://forum.notebookreview.com/acer/586065-xp-aspire-3810t.html. The user there had a similar problem.

Edited by diamant

Share this post


Link to post
Share on other sites
condor    4

I tried also this newer version. By using it I got not the described bluescreen, but instead a blackscreen with blinking cursor in the left. It seemed that meanwhile was loaded some setup data(?) in background, but I waited for ca. 30 minutes, and nothing happened.

That means: The difference between v.1.0beta7 and 1.4 is only the colour of the screen when stopping WinXP setup... :w00t:

Or maybe I simply had to wait a little bit longer than 30 minutes...? :huh:

 

Do you try XP with service pack 3?

 

Blinking cursor on left appear when partition table is incorrect/corupted or hdd damage.

Share this post


Link to post
Share on other sites
jaclaz    940

@diamant

As a side note, the given reference uses the FreeDOS FDISK as it can (just like RPM) partition the second disk, of course an internal disk (this is common on many BIOS cannot be booted as "superfloppy".

 

What the BIOS does when you switch from "SATA" to "IDE" is to change the ID of the controller, from a "specific" one to a (still specific but) IDE compatible one.

The Windows setup gets this ID and "decides" which driver to load, based on info in the .inf file coupled with the actual driver.

 

If you prefer, no matter what has been reported anywhere, there is NO way a SATA driver will be installed on a BIOS which has been set in IDE compatibility mode, unless the BIOS is seriously "botched", which, while possible in theory is very unlikely.

 

The blackscreen with blinking cursor is usually connected to an issue in bootability of the USB stick, and can usually be solved.

 

Acer has been reknown to (it has been debated if on purpose or by mistake) have a very "pesky" BIOS when it comes to USB booting, so it is entirely possible that the blinking cursor issue happened because of this, but the "mis-attribution" of the hard disk controller ID would be a "first time" 

 

Remember to add SMARTDRV for your DOS based attempt, and good luck with that approach :thumbup.

 

Should you have any issue, however, don't panic :w00t: and dont' give up :), there are several other possible ways to install an XP from a USB stick, and historically, one way or the other, we always succeeded.

 

jaclaz

Share this post


Link to post
Share on other sites
diamant    0

Do you try XP with service pack 3?

 

No; should I do so?

 

The blackscreen with blinking cursor is usually connected to an issue in bootability of the USB stick, and can usually be solved.

I have partially good news:

1.) Blinking cursor - solved :thumbup .

2.) But now new: I call it ... "34-minutes-error" :angrym: . See below.

 

1.) The solution of the problem with blinking cursor seemed to be to start the WinXP setup directly from internal HDD. I started at first  smartdrv c+  (this increases copying speed drastically). And then I went to the I386 folder (which I had copied on internal HDD), and ececuted  winnt.

 

And now I got to the "next" screen in the WinXP setup after blinking cursor! I.e. the blinking cursor appeared still, but remained only for about 1 minute - and then I could continue setup :yes: . So this problem remained no longer, but I'm now coming to...

 

2.) After the first reboot during setup I can choose "WinXP setup" (or similar) from the (automatically installed) WinXP boot manager. The setup came up to the point where devices(?) are installed. But at this point the setup froze  :no:  (also the blinking green lights down right on screen)! The setup says that there are 34 minutes remainung. I waited about more than 1 hour; nothing happened. You can see the frozen screen: post-254155-0-22182300-1417517225_thumb.

 

 

Another update: I has now an effect if I change BIOS setting from IDE to SATA/AHCI (or vice versa). I tried changing only once; after first appearance of the 34-minutes-error I rebooted with SATA/AHCI-mode for testing.

With IDE-Mode I get up to the point with the 34-minutes-error. With SATA/AHCI-mode I get the well-known bluescreen directly after selecting "WinXP Setup" in the WinXP bootmanager. So I think I should use IDE-mode for further tries.

 

Could the 34-minute-error have something to do with nLite? I used ist again before copying the WinXP setup files to the Acer's internal HDD. But this time without creating an ISO file, but only "edited" the WinXP setup folder with nLite.

I not included the AHCI_Intel_8.8.0.1009_XPx86XPx64_A.zip driver until now, because it seems not to be a textmode-driver (see the *.zip archive)?!

Share this post


Link to post
Share on other sites
condor    4

Use CPU-Z and post here screenshoot with Mainboard.

 

Also you can forget nlite and Integrate Driverpack MassStorage using DriversPacks BASE.

http://driverpacks.net/downloads

 

And to make bootable ISO with XP after masstorage integration you can use a small utility Windows Boot Image creator

 

http://www.softpedia.com/get/System/Boot-Manager-Disk/Windows-Bootable-Image-Creator.shtml

Share this post


Link to post
Share on other sites
cdob    11

No; should I do so?

Which Windows release do you use? Yes, use XP SP3 at a Core2 machine.

 

The setup says that there are 34 minutes remainung. I waited about more than 1 hour; nothing happened.

That's PNP driver installation: a device dosn't respont properly to driver loading.

If XP SP3 hangs still: fix the half broken hardware. Remove as much hardware as possible.

Test the hard disk with manufacturer tool.

Share this post


Link to post
Share on other sites
dencorso    540

Do you try XP with service pack 3?

 

No; should I do so?

Absolutely! Better still SP3 with integrated Driverpacks MassStorage, which should just work. 

Share this post


Link to post
Share on other sites
diamant    0

Good news:

WinXP is finally installed successfully now! :thumbup

 

Your tip with the SP3 was the decisive point. I downloaded and integrated SP3 with nLite - and so I could overcome this last obstacle (34-minutes-error) during WinXP install procedure.

No need of custom file ntdetect.com, no need to integrate some special Acer drivers with nLite.

 

After installation I added some drivers (Chipset, VGA driver,...) from Acer's website for that Acer notebook, but still not the AHCI driver. One thing I remarked: I changed the BIOS setting to SATA/AHCI mode (only for testing) after successful installation. With this setting WinXP no longer started. Changed it back to IDE --> WinXP started again.

I think I could maybe now install the AHCI Intel SATA AHCI Driver (8.8.0.1009) so  I would be able use the SATA/AHCI mode. But has the usage of SATA/AHCI mode any advantage compared to the IDE mode? I mean - WinXP runs fine now, actually without SATA/AHCI mode. Any suggestions?

 

 

Another thing:

I want maybe backup the data from the actually clean WinXP system by simply copying it to one (ore more) bootable DOS "backup USB stick(s)".

How to restore it if (anytime) necessary?
Could I simply format the internal HDD (again), and copy the files from USB sticks back to it?

Or will it not work (I'm thinking about problems with the boot sector and/or WinXP's boot loader).

 

Or (if anytime necessary) might it be a better strategy to delete(!) all system folders by the DOS-command  deltree  and replace them by the backuped system folders on USB-Sticks?

Share this post


Link to post
Share on other sites
dencorso    540

Yes, there's a known procedure for converting to AHCI at the point you are... I can look it up for you, in case you decide to do it.

However, IMO, the real-life gains you may accrue from such a change are minimal, except in disk benchmarks. Your system is working OK, why risk hosing it? But, in any case, if you create a full disk image (or maybe a full partition image, but that's less safe), or -- even better -- two such images and verify they are good, then there's really no risk, because you can always fall back to the point where you started, by simply redeploying the previously acquired image.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×