MBP problem: 2000:063d Write DHCS... and hang

[rastaman]

Hi all,

I have a MacBook Pro 2GHz, 1Go RAM, HD 100Go@7200RPM, and I would like to know if somebody other than me encounter this problem.

I have installed XP successfully it seems (2 stages of the install completed [the first in text mode, the second in VESA with graphical screens]) and at the first startup of Windows XP it hangs. I see the following output:
2000:0EFE: int 13_48
2000:0EFE: int 13_48
2000:0EFE: int 13_48
2000:0EFE: int 13_48
2000:0EFE: int 13_48
2000:0EFE: int 13_48
2000:0EFE: int 13_48
2000:0EFE: int 13_48
2000:0EFE: int 13_48
2000:063D: Write DCHS(128:233:203:3)L1 @00030000, LBA 00394FA0
2000:063D: Write DCHS(128:233:203:3)L1 @00030000, LBA 00394FA0

And it hangs.
So anybody have a solution for this ? I suspect that the loader try to write something like the geometry of the disk somewhere but i'm not sure (CHS : Cylinder Head Sectors ?). I would like to not erase (again, for the 3rd time) my hard drive if this is possible (and i have already try).

Also i would like to know if it exist some efi implementation which compile on MacOSX. I have tried gnu-efi but it need a complete toolchain to work it seems, and all the programs i try have problems to compile due to a bug in GCC 4.1 and 3.3 it seems. Also all the programs (including XOM i'm afraid*, although i cannot access to svn.onmac.net for the moment :-( ) i have seen seems to require VisualStudio and a windows environment :-( [so i will use gnu-efi on my debian box]

So i somebody encounter the problem i would be glad to hear about it, and if fixes have been found i will be even more happy!

Best regards to all, glad to be back to the demo' days :-) (C/ASM :-)

* strings xom.efi, hi Jesus you work with cygwin ? ;-)

[sdavis]

what you might need to try (i had problems w/the 20") is zeroing out the drive to start totally from scratch. that might be a last resort thing to do though...

[rastaman]

Hi sdavis,

Thanks for your answer but i would like to avoid this. I have done something like this multiple times last week-end and try to find a solution which doesn't require this if it exist.

As i see it Windows has been successfully installed, the only problem is this attempt to write something related to the disk (geometry?) at startup, perhaps this is needed at installation time and not after? I didn't remember seeing the "Write DCHS" message when installing.

Booted in debug mode (i can access to the boot menu of windows) the system hang after loading "mup.sys" which is, for what i have read, the last driver load before windows initialize itself [note: even if i administer W2K/3 servers in my day to day work i don't know exactly how work the boot process of Windows (even if i know/have read how the ones of Linux and FreeBSD work), so it's just a guess].

Perhaps the fact that i have my HD partitioned like this:
200Mo EFI
15 Go FAT32 (WinXP)
60 Go HFS+ (OSX)
15 Go HFS+ (was created after install, initially was MS-DOS [done with gpt add -b ... -i 3 -t windows after having unmounted /Volumes in a terminal session opened from the OSX install disk, later removed and added as -t hfs)

is the cause of my problems ? But it's strange since other people report to have successfully installed WinXP on system with more than 2 partitions ?

PS: For the bug in gcc when compiling gnu-efi, i can give further details but this is a known bug reported in a few projects (related to a substraction in a .s file - my MBP is unavailable yet to tell the exact message - (i'm re-installing Windows again [in second stage, but this always work], i would prefer to find a solution in code, this would require the same time i suppose :-))

[mpakos]

mine stop at the same spot but with a different message at the end.i press g enter and g enter again and win loads with no other prob.what g is and why it loads after that?here is a pic of it.http://img489.imageshack.us/img489/4631/img595ad.jpg (http://imageshack.us)
________
FREE XXX MOVIES (http://www.{censored}{censored}{censored}{censored}tube.c om/)

[rastaman]

Hi Mpakos,

The "g" key stand i suppose for "go" and indicate to continue the program after he has encountered an error. IIRC it was like this in the "debug" program under msdos (and other key from it work in this mode, like n (execute next instruction (and go to where it go if this is a call)). Unfortunately i haven't access to this mode after the computer hang.

I have now finished the (re-)install and there is still the same problem. What it happens is that during the first start up after installation of windows the computer hang on the grey winfows logo. After a long time (more than 3 minutes) i have stopped the computer. At the next restart, Windows display to me his last startup failed screen. I suspect that i have the same problem during the first and the second boot, but that i can only see the problem at the second boot (because at the first boot there is the grey logo and i cannot see the boot output).

I didn't desesperate and actually check if the right iastor.sys has been installed. At this point i would be glad to know if the problem i see i a problem of drivers, or a problem of mbr or something different.

I guess that this is a disk driver or mbr problem and search in this direction, but would appreciate any indication, or suggestions to debug the problem.

EDIT:typo

[Rayne]

mine stop at the same spot but with a different message at the end.i press g enter and g enter again and win loads with no other prob.what g is and why it loads after that?here is a pic of it.http://img489.imageshack.us/img489/4631/img595ad.jpg (http://imageshack.us)
your cd is not bootable and/or does not contain the patchfiles

[steve9013]

Thats exactly what happens on my iMac. G & another G gets in to Windows now, but now Windows hangs just as the desktop appears. Can't even move the mouse.

This installation used to work great! Anyone know what might have happened?

[tindeutchen]

I ran into this same error yesterday after running XP for several hours and installing many different apps. Not being able to recover I wiped the partition, reinstalled XP (again), and was testing a bunch of different applications when a reboot threw the same error again tonight. I tried the g & g and it worked great, windows came right back up. Now to figure out why. thanks for the hint, it saved several hours of my day tomorrow.

[mpakos]

if you press u also it gives you a list of commands(?) but i dont know what that is.
________
Buy silver surfer vaporizer (http://vaporizer.org/reviews/silver-surfer)

[rastaman]

if you press u also it gives you a list of commands(?) but i dont know what that is.
Hi Mpakos, thanks i will try to patch in real time if this is feasible! (well this is perhaps a lost of time since the source will soon be available but i cannot wait, i'm too enthusiast!)
Best regards,

[mpakos]

hope u make progress, i want to avoid console and boot straight to xp.
________
Toyota alessandro volta history (http://www.toyota-wiki.com/wiki/Toyota_Alessandro_Volta)

[rastaman]

Just to end the thread :
- my problem was residing in my Windows XP distribution, which ship a lot of drivers. One of them was posing the problem, since i doesn't pre-install them Windows work fine
- gcc has no problem : it's me when compiling who had forgotten some includes and so there is underfined symbol that the compiler couldn't resolve. Ouch, i'm really not a good C/ASM programmer :-)
Best regards, thanks for your help, happy to read the code soon,

EDIT:typo

[berniemac]

I'm having this exact same problem on a MacBook Pro 1.83. How exactly did you fix it?

[rastaman]

I have installed my windows distribution (winborg xp) without all the drivers. in this particular case a script named presetup.cmd was installing the drivers. I have edited it and commented each line (put "rem" at each line), so no drivers have been installed and it has worked. I haven't any idea of the driver which was causing the problem, sorry.

[berniemac]

Mine was working fine before. This just started all of a sudden. I don't believe I installed any drivers or anything.

[replicant6]

Something is up here guys. I have been running windows fine since XOM came out.

This morning, i ran into this problem. I ended up wiping my installs and I can't get it to install now. I follow the instructions EXACTLY (and i did it weeks ago successfully) and I keep getting the upside down windows logo error. It seems that the efi program wipes my XP dos partition and so when I go to install windows, it creates a partition there... I think that's my new problem.


but what's the deal with this? Do you think Apple did something in the last patch?


D

[mon]

I ran into this same error yesterday after running XP for several hours and installing many different apps. Not being able to recover I wiped the partition, reinstalled XP (again), and was testing a bunch of different applications when a reboot threw the same error again tonight. I tried the g & g and it worked great, windows came right back up. Now to figure out why. thanks for the hint, it saved several hours of my day tomorrow.


Has there been any more progress on this g & g thing? Is it indeed a driver issue? I have to do this every time on MBP 2.16 with XP SP2 and am still wondering if I have done all I can. Searching the forums for "g" is kind of hard...

[Chungy_KR]

I'm having the exact problem on my MBP 2GHz stock.
I've installed slipstreamed Korean WinXP Pro SP2, with some patching of TXTSETUP.SIF or something as instructed on wiki. And now I'm stuck on this screen, writing:
2000:063D: Write DCHS(128:797:155:23)L1 @00030000, LBA 00C38518
2000:063D: Write DCHS(128:797:155:23)L1 @00030000, LBA 00C38518

Any clues what is going wrong? By the way, this should be my first boot, and g enter g enter thing does not work, as my mac completely freezes up. and nothing works but pressing power button for 5 sec.

O yeah, if you take a look at my attachment, you can see that when I actually get 'stuck', some blue area appears. Any clues, guys? :(

[Strahd]

Hi,

The time I had this kind of issue, this was because windows was unable to boot in the native resolution (1440x900). Then I tried to change my resolution in the boot loader (when the boot loader prompt you for the OS you want to launch, press F4, then F7, and enter a little resolution (640x480). Finally, hit enter many times and select to launch windows).

This works, but windows in 640x480 :s . So I think I will reinstall the system one more time...

[jmac]

I'm encountering the same problem and can't seem to get Windows to boot any more at all (after about a week of not having any problems at all).

In my case, Windows froze immediately after (during?) installing Skype 2.0.

It seems like I'm going to have to reinstall Windows!

[mon]

I didn't have anything like this happen.
Did you try the bootcamp from apple?

[Phil_Z]

Hi,

I did use the Bootcamp from Apple and everything worked fine.
But now I downloaded and installed Skype2.0 and as soon as I start the program, my MacBookPro crashes down and restarts.
What can I do? Anyone else with this problem?

Phil

P.s: Is there any possibility to use the built-in isight camera in windows?

[mon]

I've had no crashes from the xp side although I have my Skype on the OSX side and the application will shut down there sometimes.