Register - Login
Views: 99859594
 Main - Memberlist - Active users - Calendar - Wiki - IRC Chat - Online users
Ranks - Rules/FAQ - Stats - Latest Posts - Color Chart - Smilies 		05-04-22 12:43:06 PM
Jul - Computers and Technology - Got an odd laptop problem... New poll - New thread - New reply
Next newer thread | Next older thread
Hiryuu

Level: 207


Posts: 3433/14435
EXP: 127636608
For next: 2147546

Since: 07-06-07


Since last post: 11.8 years
Last activity: 11.7 years
Posted on 06-07-08 08:44:28 PM (last edited by Komachi Onozuka at 06-07-08 05:59 PM) Link | Quote
I'm still in the midst of trying to figure this out, but I'm trying things right now nonetheless.

>>>

Here's the dilemma I've got on my hands:

I've got an old 600MHz Celeron laptop with 64 MB on it. I'm trying to make it sense a 100GB Seagate hard drive in setting up Windows XP SP2.

Here's what I already know or have tried.:

- The disk was used but should be in good, working condition (it wasn't used that long).

- The BIOS suffers from 8 GB limiting. Now this would've been a problem for me if I didn't have SP1 or greater in XP's setup which SHOULD surpass this limitation.

- XP crashes during setup with random STOP errors. The more commons ones are STOP 0x8E (during initial boot) and STOP 0x50, PAGE_FAULT_IN_NON_PAGED_AREA (during repartition/reformat failures).

- This is a Seagate drive, 100GB. In limiting it to 32GB with SeaTools, I was able to go past the initial read screen which began its 'examining XXXXXMB drive on whatever' status, which would then cause the 0x8E errors. However, when it came to deleting the partitions to start again, I could do that, but when formatting came into play, whether quick or full, whether FAT or NTFS, they would eventually fail and say 'windows was unable to format the drive'. The full format didn't seem to have a problem at all but came up with that error anyways afterwards. MAX Native mode with 100GB triggered 8Es and anything above 32 triggered 8Es. Very tricky shit.

- SeaTools, in running a long test on the drive, DID find -1- total LBA block failed but was since repaired. As far as I know, -1- LBA block isn't going to trash an entire hard drive (provided it's not track zero, which it wasn't).

What I'm trying now:

- Deleting track zero. Have yet to reboot and give XP another go because...
- Writing all zeroes to drive. This is being VERY slow with SeaTools. It's at LBA 7680 right now out of about 195mill...and I started 30m ago. A zero-fill should take way less time than this (like, 2 hours at the very most).

What I don't have:

- A way to slave up this laptop 2.5" drive to my comp to punch the partition and format it manually.
- A sound mind right about now.

>>>

Anyone got suggestions?

EDIT: New error that happens every so often:

Sometimes it'll read 100GB but after 'Searching for previous versions of Microsoft Windows...' it'll display two drives.

Drive C for 76K MB, Drive D for 19K MB. This partition information is incorrect. When I go to delete either partition, it errors out, saying the partition is no longer available. It the Stop 0x50's on me if I press ENTER.

____________________
neotransotaku
Member
wonders why OSX does not come with their version of MSPaint?
Level: 53


Posts: 320/603
EXP: 1084819
For next: 72300

Since: 08-24-07

From: The Landmark @ One Market

Since last post: 2.6 years
Last activity: 42 days
Posted on 06-08-08 05:01:53 AM Link | Quote
try using linux tools to partition the drive? Since you do not have more than 64MiB of RAM, it seems that using the USB stuff off of the RIPLinux site is not possible?

Other things you could do is use Win98 boot up disk to boot up into the command prompt and use fdisk from there. Or not use WinXP?
Hiryuu

Level: 207


Posts: 3436/14435
EXP: 127636608
For next: 2147546

Since: 07-06-07


Since last post: 11.8 years
Last activity: 11.7 years
Posted on 06-08-08 10:14:51 AM Link | Quote
Preferably, I'm going for WinXP. Eventually, I'd be dropping at least 256MB RAM on this thing when I'm all said and done. However, it's not going to happen overnight, since the RAM in this thing is dated SODIMM and I'm not exactly sure what speed it is. But, at best, this is going to be used for Word processing and MINOR work...I mean it's only a 600MHz Celery.

I will be trying UBCD later on today...if I don't get that to work, then I'm going to bring some stuff home from work to slave this thing up to defeat it in the way I intended to in the first place (should've known it wouldn't have been that easy).

____________________
Xkeeper

Level: 263


Posts: 5823/25353
EXP: 297174925
For next: 1785528

Since: 07-03-07

Pronouns: they/them/????????

Since last post: 4 days
Last activity: 58 min.
Posted on 06-08-08 05:03:50 PM Link | Quote
The random STOP errors and other things are making me wonder if other parts of the hardware aren't broke; try running memtest86+ on it?

____________________
Hiryuu

Level: 207


Posts: 3440/14435
EXP: 127636608
For next: 2147546

Since: 07-06-07


Since last post: 11.8 years
Last activity: 11.7 years
Posted on 06-08-08 09:03:40 PM Link | Quote
Long ago. Memory's not the issue it seems...even with the STOP errors pointing to possible RAM flakes (though it's not like Microsoft's 100% right on their STOP errors either...).

Got it formatting now. It found bad sectors (it was used, returned, I think I figured out why). It's taking quite a while, after verifying the drive with Ranish Partition Manager, to write the FAT tables to the disk. It's at 32% now and I started it about 5 hours ago. May be done by tomorrow but I'll have to wait until tomorrow night to verify that I can put XP on it.

If nothing else, by that time, I should have some IDE laptop cables.

____________________
Next newer thread | Next older thread
Jul - Computers and Technology - Got an odd laptop problem... New poll - New thread - New reply


Rusted Logic

Acmlmboard - commit 47be4dc [2021-08-23]
©2000-2022 Acmlm, Xkeeper, Kaito Sinclaire, et al.

28 database queries.
Query execution time: 0.074634 seconds
Script execution time: 0.015190 seconds
Total render time: 0.089824 seconds