Ok, tried other boot suggestions, still need help.

G

Guest

Ok, I have tried the bootsect, the bcdedit, and all the other command prompt
stuff for and from every drive I can think of and I get an access denied when
I try them or I get nothing at all. It looks a little like this:
E:\boot\bootsect -nt60 ALL
Target volumes will be updated with BOOTMGR compatible bootcode

C: <\\?\Volume{*insert GUID here for my XP*}>
Updated NTFS filesystem bootcode. The update may be unreliable since volume
could bot be locked during the update:
Access is denied.

I get the same on D: which is where my Vista is. Then it says
\Device\HarddiskVolume 2
Could not open the volume root directory:
The parameter is incorrect.

Bootcode was successfully updated on at least one volume.

Ok, now when I try to do the startup repair with the dvd I click on system
recovery options, it says there is a startup problem with vista and I get the
option to repair and restart. I click on that and then the box that says to
click on an OS and then goto next screen. Well, there is no OS on list and it
says something about loading a driver if its not on the list...I have no idea
what file I am supposed to use... I really would not like to have to
reinstall Vista everything time I have to reinstall XP when it screws up. Any
help would be welcome
 
G

Guest

I also forgot to say I have also tried the vistaboot pro app with no success
either. It wont even load. I get the cannot access BCD registry thing and I
am administrator and stuff. Is there an edit option for posts here?
 
C

CH

Alonea--

At that point in Startup Repair when you click load driver--it will give you a list of devices that are potential problems. If you don't see the list, try System Restore or if you had a backup image, you could try that option listed there in Recovery Options (Win RE).

You also should be able to restart and try the traditional F8 options which would include each of the safe modes for system restore and the much longer shot, Last Known Good.

Good Luck,

CH
 
C

CH

All the edit options must be used before you hit Send. I didn't see the original problem so I thought it was a no boot. Startup Repair does a scan for bad files, and includes drivers but it's not perfect. Two 3rd party apps for dealing with the boot sectors, ect. are
VistaBootPro 2.0 and Easy BCD. I can't find the full statement of your original problem. I do see below what you've used.

Take a look at

Easy BCD
http://neosmart.net/blog/archives/185


and

Vista Boot Pro
http://www.pro-networks.org/vistabootpro/intro.php

CH
 
G

Guest

Well, what happened is my XP got to the point where it would be easier to
just reformat it than try to fix it, so I cleared my C and reinstalled XP.
Vista is on D. Well, I didn't know it would mess up the boot. I am trying to
get my multiboot back with no success. I do have an update on my issue
though. I tried doing the BCDEDIT thing using the command prompt that was
under the System Restore options under the Vista Boot. Everything worked
except for the displayorder thing. When I got back into XP, the Vista Boot
Pro would load, but I can't get XP on the list and I tried using their
reinstall for the boot and still no go on getting my boot fixed. I will try
that other app you listed.
 
G

Guest

ok, I get the same error on Easy BSD as I did on Vista Boot Pro which is when
I try to add a Legacy OS to the list I get an error saying "Unhandled
exception has occurred in your application. If you click continue, the app
will ignore this error and attempt to continue. If you click Quit..." and
under that it says "Index and count must refer to a location within the
string. Parameter name: count"
The details are:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: Index and count must refer to a location
within the string.
Parameter name: count
at System.String.Remove(Int32 startIndex, Int32 count)
at
B)7pIJ)tUyAI.ACdpmRSvD.A9f569jpwVs(9RhV.AEfOUeHiTg3q.AB(FYk1tPZYtePTusExli(String , String , Int32 )
at VistaBootPRO.VistaBootPRO.btnAdd_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons
button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
ezencryption_lib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/mscorlib/2.0.0.0__b77a5c561934e089/mscorlib.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
License
Assembly Version: 1.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/mscorlib/2.0.0.0__b77a5c561934e089/mscorlib.dll
----------------------------------------
ziplib
Assembly Version: 1.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/mscorlib/2.0.0.0__b77a5c561934e089/mscorlib.dll
----------------------------------------
VistaBootPRO
Assembly Version: 2.1.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/mscorlib/2.0.0.0__b77a5c561934e089/mscorlib.dll
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

I still don't get why when I got into recovery thing under vista boot it
scans for problems, sees that the boot is messed and says it will repair and
restart and does nothing but goto that repair screen asking which OS, which
there is none on the list...To be clear, i am completely unable to get into
Vista, period. I can get into XP for that is all thats what loads when I
start my computer.
 
C

Colin Barnhorst

The resolution is to copy bcdedit.exe from
Vista %systemroot%\Windows\System32
folder to VistaBoot Pro. Then it will work. The versions are out of sync.
 
C

CH

Allonea--

Maybe something in this KB will help you. Rule #1 (not preaching, and the public download notes and notes with any Vista build are always install the older OS first. See if anything here will help you:

Windows Vista no longer starts after you install an earlier version of the Windows operating system in a dual-boot configuration
http://support.microsoft.com/kb/919529/en-us

CH
 
G

Guest

Ok, I tried that, now my Vista Boot is worse. I am getting an error almost
every screen now saying "Index and count must refer to a location within the
string. Parameter name: Count". So no, that did not work...
 
G

Guest

Have that page in my favourites from earlier. When I do those steps in
command prompt under windows XP, none of it will work. If I use command
prompt under the Vista boot, everything works until I get to:
Drive:\Windows\system32\Bcdedit –displayorder {ntldr} –addlast
No matter how I phrase it I can't seem to get that step to work...
Also that kinda sucks that if you wanna fix one of your os' you have to
reinstall all of them. Kinda bs to me. I mean, I understand that its better
to install older first, which is what I did the first time around, but I
can't help it if XP screws up and the best way to fix it is reinstall it.
 
C

CH

I feel your pain Alonea. There are people on here who have more experience with BCDEDIT and its switches. Hopefully they will chime in. I wish I knew if the setup teams could have architected these boot editors better or if they have room for improvmeent with them. From what I know of the setup team, they are looking for every angle to make things as easy as possible. Links like these are probably old news for you:


Boot Configuration Data Editor Frequently Asked Questions
http://www.microsoft.com/technet/windowsvista/library/85cd5efe-c349-427c-b035-c2719d4af778.mspx

Of course you can define the switches of BCEDIT at the cmd prompt bcdedit /? and then drill into each switch.

CH
 
G

Guest

Yeah, I ended up going through their little manual (the link) earlier today
and also under bcdedit and I still can't get the deviceorder step to work. I
get "An error has occurred setting the element data. The system cannot find
the file specified. Which usually means you either typed it wrong or
something else is screwy...which is just my luck. But in my frustration I did
manage to make myself laugh hysterically...
D:\Windows\System32>die a horrible death
'die' is not recognized as an internal or external command, operable
program, or batch file.
I have no idea why that is horribly amusing to me...it just is.
 
C

CH

It is funny--I find it funny. Susie Essman from Curb Your Enthusiasm (plays Suzie Green) who is a wickedly funny stand up comic would find it funny. She was featured on ABC Nightline tonight, and she said that a tremendous amount of humor is anchored in anger. I guess you were aiming at either killing Windoz or killing the cmd prompt.

But the Bush Right Wing Religious zealots wouldn't think so at all. This is unrelated, but I like to try to see if I can do novel things with the run box and cmd prompt.

If you turn on the telnet service--it's a security vulnerability so in XP it's of course default on because of course MSFT is the premier security company so if you type

telnet towel.blinkenlights.nl

in the run box you'll get Star Wars in ASCII on your cmd screen. The telnet service has to be on. It is by default in XP, and in Vista you can add it by:

There is a way to install it - Control Panel -> Programs -> Turn on off windows feature -> check telnet client

As to the

D:\Windows\System32>die a horrible death
'die' is not recognized as an internal or external command, operable
program, or batch file.

1) You should start a blog with screenshots and of things like this-- I have collections of ridiculous Windows errors stashed on an XP boot.

2) It is important for you to know that there is an MSKB that has the words in the title "All this stuff." It's very ITesque.

RAM, Virtual Memory, Pagefile and all that stuff
http://support.microsoft.com/kb/555223/en-us

I get kind of amused at the way IT types use stitled language for such mundane items sometimes. I also think it's funny that no one from MSFT can seem to get up and make a live presentation if they have anything to do with Office without the word leverage. Technet doesn't do this but anyone connected with Sales has it programmed into their DNA.

3) You owe it to yourself to watch a DVD of Genine Garofalo live. Most of it is improv and plays off the audience.

4) You owe it to yourself to watch Susie Essman who plays Susie Green on HBO's "Curb Your Enthusiasm".
http://www.hbo.com/larrydavid/asksusie/archive.html

I wish I could be of more help with BCDedit. Hopefully someone will have a way past this soon.

CH
 
M

MICHAEL

I love 'Curb Your Enthusiasm'.

This is funny stuff:

http://www.hbo.com/larrydavid/asksusie/archive.html
Ask Susie


-Michael
---------------------
It is funny--I find it funny. Susie Essman from Curb Your Enthusiasm (plays Suzie Green) who
is a wickedly funny stand up comic would find it funny. She was featured on ABC Nightline
tonight, and she said that a tremendous amount of humor is anchored in anger. I guess you were
aiming at either killing Windoz or killing the cmd prompt.

But the Bush Right Wing Religious zealots wouldn't think so at all. This is unrelated, but I
like to try to see if I can do novel things with the run box and cmd prompt.

If you turn on the telnet service--it's a security vulnerability so in XP it's of course
default on because of course MSFT is the premier security company so if you type

telnet towel.blinkenlights.nl

in the run box you'll get Star Wars in ASCII on your cmd screen. The telnet service has to be
on. It is by default in XP, and in Vista you can add it by:

There is a way to install it - Control Panel -> Programs -> Turn on off windows feature ->
check telnet client

As to the

D:\Windows\System32>die a horrible death
'die' is not recognized as an internal or external command, operable
program, or batch file.

1) You should start a blog with screenshots and of things like this-- I have collections of
ridiculous Windows errors stashed on an XP boot.

2) It is important for you to know that there is an MSKB that has the words in the title "All
this stuff." It's very ITesque.

RAM, Virtual Memory, Pagefile and all that stuff
http://support.microsoft.com/kb/555223/en-us

I get kind of amused at the way IT types use stitled language for such mundane items
sometimes. I also think it's funny that no one from MSFT can seem to get up and make a live
presentation if they have anything to do with Office without the word leverage. Technet
doesn't do this but anyone connected with Sales has it programmed into their DNA.

3) You owe it to yourself to watch a DVD of Genine Garofalo live. Most of it is improv and
plays off the audience.

4) You owe it to yourself to watch Susie Essman who plays Susie Green on HBO's "Curb Your
Enthusiasm".
http://www.hbo.com/larrydavid/asksusie/archive.html

I wish I could be of more help with BCDedit. Hopefully someone will have a way past this soon.

CH
 
G

Guest

Yup, love that show too. Now any more suggestions out there for fixing this
bloody boot? Or know why I am getting that error thing on Vista Boot Pro when
I try to add a legacy os to the list? (btw, I reinstalled it, so I can
navigate it pretty much, but still error on the modify list) Or anyone want
to explain how to use the startup repair in a nice little step by step
because I am still lost on that.
 
C

CH

Alonea--

I thought I did explain how to use Startup Repair in a nice little step by step. I've done a bunch of threads in the last 24 so maybe I didn't get to startup repair in this one. I'm going to tell you what it can do>going to give you the step by step> and you have no downside for trying it.

What It Can Do:

If you run Win RE's Startup Repair in Vista, it will try to check and repair the following and we're taking about under three minutes usually when it works which is often: (this is not a complete list but a list of major tasks it can perform):

Registry Corruptions

Missing/corrupt driver files (you don't have to guess here--it looks at all of them

Missing/corrupt system files (disabled in Beta 2 as is System File Checker but present newer builds)

Incompatible Driver Installation

Incompatible OS update installations

Startup Repair may offer a dialogue box to use System restore.

How to Use Startup Repair:

***Accessing Windows RE (Repair Environment):***

1) Insert Media into PC (the DVD you burned)

2) ***You will see on the Vista logo setup screen after lang. options in the
lower left corner, a link called "System Recovery Options."***

Screenshot: System Recovery Options (Lower Left Link)
http://blogs.itecn.net/photos/liuhui/images/2014/500x375.aspx

Screenshot: (Click first option "Startup Repair"
http://www.leedesmond.com/images/img_vista02ctp-installSysRecOpt2.bmp

3) Select your OS for repair.

4) Its been my experience that you can see some causes of the crash from
theWin RE feature:

You'll have a choice there of using:

1) Startup Repair
2) System Restore
3) Complete PC Restore

Don't curb your enthusiasn Alonea. You can do this. Any questions, lemme know.

CH
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

bootsect problem 4
Help please :( 1
Duel Boot Problem 3
How to fix MBR for Vista 4
Boot manager location 4
Possible to dual boot across 2 HDs? 5
Need help with Boot sector verification 0
Need help with verifying Boot partition 0

Top