A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows 7 » Windows 7 Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Virtual XP won't start



 
 
Thread Tools Rate Thread Display Modes
  #16  
Old April 21st 17, 11:21 AM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 1,517
Default Virtual XP won't start

Roger Mills wrote:
On 21/04/2017 10:23, Paul wrote:

Summary: Delete the .vsv and retry... You're deleting the
hiberfile when doing that, and Windows could (worst case)
need to tidy up on the next run, using CHKDSK.

Paul



Thanks. I'll have a close look at that.


In a way, this is like real physical machines. If you
hibernate WinXP over and over and over again... eventually
it'll fall over. Things like memory errors, even if the
background rate is low, can accumulate over time. and it's
not clear there is any recovery mechanism for hiberated
machines - short of truly shutting them down and
rebooting them properly.

The default setup when I tested just now, is the Settings
panel for Virtual PC defines "Power button = hibernate".
I changed from the default, selected "Shutdown" instead,
and the .vsv file can disappear at shutdown as a result.

To operate the machine, instead of using "logout" in the
Start menu, I've been using my old standby, the Alt-F4
hotkey sequence. As that offers the rest of the shutdown
options. You should also be able to get that from Task
Manager, if you wanted.

I'm surprised mine hasn't tipped over yet, I've been
having so much fun with it. Windows Updates... almost done.

Have fun,
Paul
Ads
  #17  
Old April 21st 17, 11:46 PM posted to alt.windows7.general
Roger Mills[_2_]
external usenet poster
 
Posts: 250
Default Virtual XP won't start

On 21/04/2017 11:21, Paul wrote:
Roger Mills wrote:
On 21/04/2017 10:23, Paul wrote:

Summary: Delete the .vsv and retry... You're deleting the
hiberfile when doing that, and Windows could (worst case)
need to tidy up on the next run, using CHKDSK.

Paul



Thanks. I'll have a close look at that.


In a way, this is like real physical machines. If you
hibernate WinXP over and over and over again... eventually
it'll fall over. Things like memory errors, even if the
background rate is low, can accumulate over time. and it's
not clear there is any recovery mechanism for hiberated
machines - short of truly shutting them down and
rebooting them properly.

The default setup when I tested just now, is the Settings
panel for Virtual PC defines "Power button = hibernate".
I changed from the default, selected "Shutdown" instead,
and the .vsv file can disappear at shutdown as a result.

To operate the machine, instead of using "logout" in the
Start menu, I've been using my old standby, the Alt-F4
hotkey sequence. As that offers the rest of the shutdown
options. You should also be able to get that from Task
Manager, if you wanted.

I'm surprised mine hasn't tipped over yet, I've been
having so much fun with it. Windows Updates... almost done.

Have fun,
Paul


My virtual machine is set to shut down when the application closes. I
can't find any .vsv.files.

My wife's main computer at home is still running XP. When we go away
from home (we're away now) for a few days we take the Win 7 Pro laptop
and she uses the Virtual XP Machine on it. Her data is all on an
external USB drive, so we're not desperate to get at the data on the
virtual machine, but it's annoying that she can't run her legacy
applications.

This was set up using the laptop's original HDD - which was then cloned
onto an SSD. I think the HDD is still intact in a cupboard back at home.
I'm tempted to copy all of the virtual machine files from that onto the
SSD, on the assumptions that the files on the SSD have somehow got
corrupted. Do you think that might work?
--
Cheers,
Roger
____________
Please reply to Newsgroup. Whilst email address is valid, it is seldom
checked.
  #18  
Old April 22nd 17, 12:02 AM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 1,517
Default Virtual XP won't start

Roger Mills wrote:


My virtual machine is set to shut down when the application closes. I
can't find any .vsv.files.

My wife's main computer at home is still running XP. When we go away
from home (we're away now) for a few days we take the Win 7 Pro laptop
and she uses the Virtual XP Machine on it. Her data is all on an
external USB drive, so we're not desperate to get at the data on the
virtual machine, but it's annoying that she can't run her legacy
applications.

This was set up using the laptop's original HDD - which was then cloned
onto an SSD. I think the HDD is still intact in a cupboard back at home.
I'm tempted to copy all of the virtual machine files from that onto the
SSD, on the assumptions that the files on the SSD have somehow got
corrupted. Do you think that might work?


The issue with cloning the contents of the VHD file, is
"activation". I've occasionally attempted to move OSes protected
by activation, and was met by the OS "freezing", even though
it had drivers suitable to finish booting. To my mind,
the experiment is worth doing, but without an absolute
guarantee you'll benefit from it.

The idea of moving the OS to physical level, is in the
hope it's more visible during boot (i.e. Safe Mode, F8,
enable Boot Logging, or whatever). Just so you can get
a hint as to what is busted.

While Windows Virtual PC is "inflating" the .vsv file when
the VM runs, you don't have an interface to watch. That's
because Terminal Services (the chosen display method)
is not available until the thing is running. If you were
to run the same VM on VPC2007, and it wasn't using
Terminal Services, you might get to see more of the
boot sequence.

These are the only ideas that come to mind. Having watched
it start, I cannot think of anything else to try (due to
the lack of visibility during the boot phase).

The WinXP Mode VM, also runs on VMWare. VMWare had a special
deal with Microsoft, where they agreed to enforce the usage
requirement (could only boot the VM is Win7Pro or better
was the Host), so that's another way to do it. Only a single
version of VMWare supported this. So if say, VMWare today
was Version 7, maybe it was Version 4 or so that supported
WinXP Mode guests. I'm not a VMWare user, so haven't
tried that, and I don't even have a VMWare setup here.

And the purpose of any experiment, is "observation" and figuring
out what subsystem on WinXPMode is busted. As the current running
environment is "useless" for debugging.

I had high hopes you had a hibernating machine, and simply
deleting the .vsv would be enough... Oh, well.

Paul

  #19  
Old April 22nd 17, 12:07 AM posted to alt.windows7.general
T
external usenet poster
 
Posts: 990
Default Virtual XP won't start

On 04/17/2017 03:40 PM, Roger Mills wrote:
I have a Virtual XP setup for running a few legacy programs which won't
run on W7-64bit. It's on a laptop running W7-PRO 64.

It's been ok for several years, but today it won't start. It puts up the
usual little window saying "Starting Virtual Machine" and the progress
marker starts moving to the right and when it's got about one third of
the way across after about 40 seconds, the window closes - and that's
that. No error messages or anything. At the point when it closes, I
would expect it to say "Starting integration functions" - or something
like that - but it doesn't.

I've re-booted numerous times to no avail. Malwarebytes doesn't find
anything amiss.

Anyone got any suggestions what to try next?

TIA.



Hi Roger,

This is a little late, but often times your can run XP
programs from Window 7 by installing directly into
your C:\ drive, rather than C:\Program Files...

For instance
c:\lotus

For lotus Smart Suite.

-T


  #20  
Old April 22nd 17, 01:03 AM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 1,517
Default Virtual XP won't start

Paul wrote:
Roger Mills wrote:


My virtual machine is set to shut down when the application closes. I
can't find any .vsv.files.

My wife's main computer at home is still running XP. When we go away
from home (we're away now) for a few days we take the Win 7 Pro laptop
and she uses the Virtual XP Machine on it. Her data is all on an
external USB drive, so we're not desperate to get at the data on the
virtual machine, but it's annoying that she can't run her legacy
applications.

This was set up using the laptop's original HDD - which was then
cloned onto an SSD. I think the HDD is still intact in a cupboard back
at home. I'm tempted to copy all of the virtual machine files from
that onto the SSD, on the assumptions that the files on the SSD have
somehow got corrupted. Do you think that might work?


The issue with cloning the contents of the VHD file, is
"activation". I've occasionally attempted to move OSes protected
by activation, and was met by the OS "freezing", even though
it had drivers suitable to finish booting. To my mind,
the experiment is worth doing, but without an absolute
guarantee you'll benefit from it.

The idea of moving the OS to physical level, is in the
hope it's more visible during boot (i.e. Safe Mode, F8,
enable Boot Logging, or whatever). Just so you can get
a hint as to what is busted.

While Windows Virtual PC is "inflating" the .vsv file when
the VM runs, you don't have an interface to watch. That's
because Terminal Services (the chosen display method)
is not available until the thing is running. If you were
to run the same VM on VPC2007, and it wasn't using
Terminal Services, you might get to see more of the
boot sequence.

These are the only ideas that come to mind. Having watched
it start, I cannot think of anything else to try (due to
the lack of visibility during the boot phase).

The WinXP Mode VM, also runs on VMWare. VMWare had a special
deal with Microsoft, where they agreed to enforce the usage
requirement (could only boot the VM is Win7Pro or better
was the Host), so that's another way to do it. Only a single
version of VMWare supported this. So if say, VMWare today
was Version 7, maybe it was Version 4 or so that supported
WinXP Mode guests. I'm not a VMWare user, so haven't
tried that, and I don't even have a VMWare setup here.

And the purpose of any experiment, is "observation" and figuring
out what subsystem on WinXPMode is busted. As the current running
environment is "useless" for debugging.

I had high hopes you had a hibernating machine, and simply
deleting the .vsv would be enough... Oh, well.

Paul


Well forget this. It seems to start a brand new WinXP Mode
machine, and doesn't just "import" the VHD you've already got.

http://www.duxburysystems.com/docume...ots/vmware.htm

Even though you can get the player, it's not going to help.

http://www.oldapps.com/VMware_player...=6994?download

Paul
  #21  
Old April 22nd 17, 01:06 AM posted to alt.windows7.general
T
external usenet poster
 
Posts: 990
Default Virtual XP won't start

On 04/21/2017 05:03 PM, Paul wrote:
Paul wrote:
Roger Mills wrote:


My virtual machine is set to shut down when the application closes. I
can't find any .vsv.files.

My wife's main computer at home is still running XP. When we go away
from home (we're away now) for a few days we take the Win 7 Pro
laptop and she uses the Virtual XP Machine on it. Her data is all on
an external USB drive, so we're not desperate to get at the data on
the virtual machine, but it's annoying that she can't run her legacy
applications.

This was set up using the laptop's original HDD - which was then
cloned onto an SSD. I think the HDD is still intact in a cupboard
back at home. I'm tempted to copy all of the virtual machine files
from that onto the SSD, on the assumptions that the files on the SSD
have somehow got corrupted. Do you think that might work?


The issue with cloning the contents of the VHD file, is
"activation". I've occasionally attempted to move OSes protected
by activation, and was met by the OS "freezing", even though
it had drivers suitable to finish booting. To my mind,
the experiment is worth doing, but without an absolute
guarantee you'll benefit from it.

The idea of moving the OS to physical level, is in the
hope it's more visible during boot (i.e. Safe Mode, F8,
enable Boot Logging, or whatever). Just so you can get
a hint as to what is busted.

While Windows Virtual PC is "inflating" the .vsv file when
the VM runs, you don't have an interface to watch. That's
because Terminal Services (the chosen display method)
is not available until the thing is running. If you were
to run the same VM on VPC2007, and it wasn't using
Terminal Services, you might get to see more of the
boot sequence.

These are the only ideas that come to mind. Having watched
it start, I cannot think of anything else to try (due to
the lack of visibility during the boot phase).

The WinXP Mode VM, also runs on VMWare. VMWare had a special
deal with Microsoft, where they agreed to enforce the usage
requirement (could only boot the VM is Win7Pro or better
was the Host), so that's another way to do it. Only a single
version of VMWare supported this. So if say, VMWare today
was Version 7, maybe it was Version 4 or so that supported
WinXP Mode guests. I'm not a VMWare user, so haven't
tried that, and I don't even have a VMWare setup here.

And the purpose of any experiment, is "observation" and figuring
out what subsystem on WinXPMode is busted. As the current running
environment is "useless" for debugging.

I had high hopes you had a hibernating machine, and simply
deleting the .vsv would be enough... Oh, well.

Paul


Well forget this. It seems to start a brand new WinXP Mode
machine, and doesn't just "import" the VHD you've already got.

http://www.duxburysystems.com/docume...ots/vmware.htm

Even though you can get the player, it's not going to help.

http://www.oldapps.com/VMware_player...=6994?download

Paul


Virtual Box ?
  #22  
Old April 22nd 17, 02:08 AM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 1,517
Default Virtual XP won't start

T wrote:
On 04/21/2017 05:03 PM, Paul wrote:
Paul wrote:
Roger Mills wrote:


My virtual machine is set to shut down when the application closes. I
can't find any .vsv.files.

My wife's main computer at home is still running XP. When we go away
from home (we're away now) for a few days we take the Win 7 Pro
laptop and she uses the Virtual XP Machine on it. Her data is all on
an external USB drive, so we're not desperate to get at the data on
the virtual machine, but it's annoying that she can't run her legacy
applications.

This was set up using the laptop's original HDD - which was then
cloned onto an SSD. I think the HDD is still intact in a cupboard
back at home. I'm tempted to copy all of the virtual machine files
from that onto the SSD, on the assumptions that the files on the SSD
have somehow got corrupted. Do you think that might work?

The issue with cloning the contents of the VHD file, is
"activation". I've occasionally attempted to move OSes protected
by activation, and was met by the OS "freezing", even though
it had drivers suitable to finish booting. To my mind,
the experiment is worth doing, but without an absolute
guarantee you'll benefit from it.

The idea of moving the OS to physical level, is in the
hope it's more visible during boot (i.e. Safe Mode, F8,
enable Boot Logging, or whatever). Just so you can get
a hint as to what is busted.

While Windows Virtual PC is "inflating" the .vsv file when
the VM runs, you don't have an interface to watch. That's
because Terminal Services (the chosen display method)
is not available until the thing is running. If you were
to run the same VM on VPC2007, and it wasn't using
Terminal Services, you might get to see more of the
boot sequence.

These are the only ideas that come to mind. Having watched
it start, I cannot think of anything else to try (due to
the lack of visibility during the boot phase).

The WinXP Mode VM, also runs on VMWare. VMWare had a special
deal with Microsoft, where they agreed to enforce the usage
requirement (could only boot the VM is Win7Pro or better
was the Host), so that's another way to do it. Only a single
version of VMWare supported this. So if say, VMWare today
was Version 7, maybe it was Version 4 or so that supported
WinXP Mode guests. I'm not a VMWare user, so haven't
tried that, and I don't even have a VMWare setup here.

And the purpose of any experiment, is "observation" and figuring
out what subsystem on WinXPMode is busted. As the current running
environment is "useless" for debugging.

I had high hopes you had a hibernating machine, and simply
deleting the .vsv would be enough... Oh, well.

Paul


Well forget this. It seems to start a brand new WinXP Mode
machine, and doesn't just "import" the VHD you've already got.

http://www.duxburysystems.com/docume...ots/vmware.htm

Even though you can get the player, it's not going to help.

http://www.oldapps.com/VMware_player...=6994?download

Paul


Virtual Box ?


Just got it running.

This is fiddly to do (but possible), if the virtual machine is healthy.
Here is the result. It didn't freeze on me. It came damn close.

https://s17.postimg.org/jt66hiz0f/wi...virtualbox.gif

*******

OK, so the first challenge is, if you check back in VirtualPC,
look at the settings for the WinXPMode machine, the VHD disk is
termed a "differencing disk". It isn't a vanilla VHD after all.
VirtualBox doesn't like that VHD at all.

Windows Virtual PC has a "Merge" function. I asked it to merge
the winxpmode.vhd file and make me a new file I called "pig.vhd".
After some amount of grinding, there as a new 5GB pig.vhd file.

I thought for a moment, I'd lost some of the files from the
VirtualPC folder, but they all seem to be back now.

I exited VirtualPC.

I fired up VirtualBox and defined a "New" machine. Declared
it as a WinXP 32 bit machine. Set the memory size to the same
value as the VM used in VirtualPC.

When it came to the Storage node, the CD was already there.
Using the "pig.vhd" file, it's not a differencing disk, but
just a plain VHD, and that attached no problem, as an IDE
drive. Since WinXP does not have a native AHCI driver, you
don't want to attach it to a SATA controller, where AHCI is
the default. The CD is connected to IDE, and "pig.vhd" ends
up on the same IDE controller.

The fun begins, when you try to boot it :-(

The mouse doesn't work worth a damn. I went to the top menu bar
on the running VM, and selected "Insert VM Additions". As (obvious
after a moment of thought), the so-called hardware drivers are
going to be screwed up. Now, I thought a HID was a HID, but it
bucked and fought with me all the way.

I had to dismiss the "new hardware" dialog, interfering with my
attempts to us the VirtualBox additions dialog. Since the dialog
uses the letter "C" for Continue, I was able to "feed" the dialog
control input and coax it along the way.

After the additions were installed, it was time to restart. Well,
the virtual machine would not shut down. I got a black screen.

After giving it a reset from the menu, it started to boot. Things
behaved better after that point.

Now, if the problem Roger is having, happens before the desktop
even appears, he might not get that far.

But it looks like, at least, "yes", you can get the basic machine
running. It is no longer activated, as you can see in my picture above.
This is not intended as a long term solution. Since all the disk
changes should be to the merge output "pig.vhd", I think my original
WinXPMode remains undamaged.

You could try pressing F8 early in the first boot, and try to
get it into Safe Mode.

Now, if you did effect some changes in "pig.vhd", how would you
get them back to the original machine ? I think VirtualPC is a bit
more forgiving of "disk additions", so you can modify the disk
entry in the settings dialog, and try "pig.vhd" in place of the
original "windows XP Mode.vhd" file. After you'd exited VirtualBox
of course.

https://www.virtualbox.org/

On bringing "pig.vhd" back, the activation will likely remain broken.
The "Windows XP Mode.vmcx" file, a VirtualPC text file, contains
a bunch of GUID identifiers, intended to break things, which will
contribute to your misery.

The only hope from all of this, is that a root cause can be found,
a fix applied (somehow) to the differencing disk, and injected
without damaging anything.

Paul
  #23  
Old April 22nd 17, 02:40 AM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 1,517
Default Virtual XP won't start

Roger Mills wrote:
On 21/04/2017 11:21, Paul wrote:
Roger Mills wrote:
On 21/04/2017 10:23, Paul wrote:

Summary: Delete the .vsv and retry... You're deleting the
hiberfile when doing that, and Windows could (worst case)
need to tidy up on the next run, using CHKDSK.

Paul


Thanks. I'll have a close look at that.


In a way, this is like real physical machines. If you
hibernate WinXP over and over and over again... eventually
it'll fall over. Things like memory errors, even if the
background rate is low, can accumulate over time. and it's
not clear there is any recovery mechanism for hiberated
machines - short of truly shutting them down and
rebooting them properly.

The default setup when I tested just now, is the Settings
panel for Virtual PC defines "Power button = hibernate".
I changed from the default, selected "Shutdown" instead,
and the .vsv file can disappear at shutdown as a result.

To operate the machine, instead of using "logout" in the
Start menu, I've been using my old standby, the Alt-F4
hotkey sequence. As that offers the rest of the shutdown
options. You should also be able to get that from Task
Manager, if you wanted.

I'm surprised mine hasn't tipped over yet, I've been
having so much fun with it. Windows Updates... almost done.

Have fun,
Paul


My virtual machine is set to shut down when the application closes. I
can't find any .vsv.files.

My wife's main computer at home is still running XP. When we go away
from home (we're away now) for a few days we take the Win 7 Pro laptop
and she uses the Virtual XP Machine on it. Her data is all on an
external USB drive, so we're not desperate to get at the data on the
virtual machine, but it's annoying that she can't run her legacy
applications.

This was set up using the laptop's original HDD - which was then cloned
onto an SSD. I think the HDD is still intact in a cupboard back at home.
I'm tempted to copy all of the virtual machine files from that onto the
SSD, on the assumptions that the files on the SSD have somehow got
corrupted. Do you think that might work?


Another thing that comes to mind, is you could stay in Virtual PC world,
go to the Settings box for the WinXPMode machine, and set the CD to point
to your ISO9660 copy of WinXP SP3 (an installer CD of SP3 level).

First, boot to command prompt on the CD. There is an option, to instead
of installing, do some repairs. And the Command Prompt is an option there.
You could run CHKDSK. (Before you try that, you want to back up the
virtual machine files, in case it fouls up. CHKDSK is a repair in place
utility, which can damage things, just as easily as it can fix them.)

If the volume has good NTFS properties, you could then try booting
a second time, and do a Repair Install. Afterwards, you'd have to
redo your Windows Update, put back IE8 or whatever, which is still
a lot of work. But it might be a way to recover your previous setup,
assuming no other triage is possible.

One problem with doing that, so going to be the activation...
Will it activate automatically ? I don't think there's a chance in
hell that will happen. So right away, I can see this being a non-starter.

It's becoming clearer now, that best practice with the "crap",
is frequent backups (Macrium, Acronis, Ghost, or whatever). As
long as you have previous copies of the "Windows XP Mode.vhd" file,
you'll be in good company. And since, by default, it's not merged,
both the parent and child (the big VHD) have to be captured.
If the VHD is merged (disabling differencing, making the output
file of the merge operation the primary VHD file), then only the
one file would need to be kept.

7-ZIP can normally open regular VHD files. I use this for getting
files out of virtual machines for example. However, the "Windows XP Mode.vhd"
file is a "child" (according to the VirtualBox labeling), and 7-ZIP
cannot handle the header format differences and refuses to open it.
So yet another option I was counting on, didn't work. The merged file
on the other hand ("pig.vhd"), that worked fine. Let's hope that "merging"
is not dependent on the virtual disk health to work.

Paul
  #24  
Old April 23rd 17, 11:46 PM posted to alt.windows7.general
tesla sTinker
external usenet poster
 
Posts: 44
Default Virtual XP won't start

should of emailed me...
I dont always hang on this group..

You know how to rename a file dont you?
Its that simple, you just have to find the old dated one that is the
backup of it. Then rename it after you have moved the other one and put
the backup in its place, so that its named exactly the same as the one
that is messed up. But copy that one to a folder that you make calling
it, old file system file.... Or something that you want to call it, so
if you need it again, you can just revert back to it in case you choose
poorly of which one is the good backup. There may be more than one
backup file of it. Depending on how much the machine has been used...


The path should be, C; Windows / System32 / config /
You will find it in there inside config folder...
The name should be SYSTEM in all capital letters.
The Type should be File
The Size should be about 17 mb, mine is little more than that....


Now, you might have a folder inside that config folder named RegBack.
Look in there also, to find another one of the same type file that says
on it, SYSTEM and check the size of it, and the Date. The Date
modified should be older, the one on the one that fires up the machine
in the config folder, should be the same date as now time, for its
always modified every time you start the machine....

so what you need to do, is make sure both those files are about the same
size. They should be. The one in the RegBack folder, and the one in
the config folder. Then, if they are, change them, but do not swap
them. What I did, was a I made a new folder in the config folder,
labeling it NewBkp... So that it was not the same as RegBack. And then
I took the SYSTEM file, and cut and paste it from the config folder,
into the NewBkp folder. That way, you know where it is. And, this
will keep you from renaming in it or having to rename it as long as you
do all this in its proper order.... This first of course. Then go in
the RegBack folder, and just copy that one into the config folder, and
when it ask you do you want to replace it, say yes.

Then after that, your done. Turn the machine off like you normally do,
and then restart it again.....

On 4/19/2017 3:27 PM, Roger Mills wrote:
On 19/04/2017 21:43, tesla sTinker wrote:


On 4/18/2017 10:34 AM, Roger Mills wrote:
On 18/04/2017 14:37, philo wrote:
On 04/17/2017 07:55 PM, Dave Doe wrote:
In article , ,
Roger Mills says...

I have a Virtual XP setup for running a few legacy programs which
won't
run on W7-64bit. It's on a laptop running W7-PRO 64.

It's been ok for several years, but today it won't start. It puts up
the
usual little window saying "Starting Virtual Machine" and the
progress
marker starts moving to the right and when it's got about one
third of
the way across after about 40 seconds, the window closes - and that's
that. No error messages or anything. At the point when it closes, I
would expect it to say "Starting integration functions" - or
something
like that - but it doesn't.

I've re-booted numerous times to no avail. Malwarebytes doesn't find
anything amiss.

Anyone got any suggestions what to try next?

Go into Windows Update and see if you have KB2830477 installed.

If you have, remove it. And try VPC again.




That update is three years old, I would expect a more recent update to
be the possible problem.

Indeed. But I've uninstalled the other updates which have been installed
since Virtual XP last worked - to no avail!

dont do that..... your system file is likely corrupt. Go change it
manually. Its inside the windows/system folder. There is a backup that
is kept in the same folder with it somewhere, with a funny extension
name. sometimes even more than one of them. Its just a configuration
file that starts up the machine.... Sometimes they get corrupt. And
then, it don't work anymore... its not the update, so you need to leave
that alone...


So how do I go about restoring the system file?

  #25  
Old April 24th 17, 12:01 AM posted to alt.windows7.general
tesla sTinker
external usenet poster
 
Posts: 44
Default Virtual XP won't start

should of emailed me...
I dont always hang on this group..

You know how to rename a file dont you?
Its that simple, you just have to find the old dated one that is the
backup of it. Then rename it after you have moved the other one and put
the backup in its place, so that its named exactly the same as the one
that is messed up. But copy that one to a folder that you make calling
it, old file system file.... Or something that you want to call it, so
if you need it again, you can just revert back to it in case you choose
poorly of which one is the good backup. There may be more than one
backup file of it. Depending on how much the machine has been used...


The path should be, C; Windows / System32 / config /
You will find it in there inside config folder...
The name should be SYSTEM in all capital letters.
The Type should be File
The Size should be about 17 mb, mine is little more than that....


Now, you might have a folder inside that config folder named RegBack.
Look in there also, to find another one of the same type file that says
on it, SYSTEM and check the size of it, and the Date. The Date
modified should be older, the one on the one that fires up the machine
in the config folder, should be the same date as now time, for its
always modified every time you start the machine....

so what you need to do, is make sure both those files are about the same
size. They should be. The one in the RegBack folder, and the one in
the config folder. Then, if they are, change them, but do not swap
them. What I did, was a I made a new folder in the config folder,
labeling it NewBkp... So that it was not the same as RegBack. And then
I took the SYSTEM file, and cut and paste it from the config folder,
into the NewBkp folder. That way, you know where it is. And, this
will keep you from renaming in it or having to rename it as long as you
do all this in its proper order.... This first of course. Then go in
the RegBack folder, and just copy that one into the config folder, and
when and if it ask you do you want to replace, say yes.
IF it asks... I mean if you copy instead of cut, it may still be there.
So it would ask this question. Now, there is the other option, under
your right clik of mouse, its called, restore previous versions.
Instead of doing all this... So just then find the folder config, in
there is the file named SYSTEM, And right clik on it, and you will see
this option in the menu, which is alot faster yes. But, as i said, you
may have more than one backup, and if you do, then you want to be picky
about dates,,,,,,


Then after all that, your done. Turn the machine off like you normally
do, and then restart it up again..... It should be more healthy if you
succeeded.

And if not, just undo the cut and paste copy. In restore previous
versions option, you dont have to move it at all, it will guide you to
do it..... It is easier and safer for those who do not know much
about computers.... We did it the manual way.... But both ways are
the same.....

On 4/19/2017 3:27 PM, Roger Mills wrote:
On 19/04/2017 21:43, tesla sTinker wrote:


On 4/18/2017 10:34 AM, Roger Mills wrote:
On 18/04/2017 14:37, philo wrote:
On 04/17/2017 07:55 PM, Dave Doe wrote:
In article , ,
Roger Mills says...

I have a Virtual XP setup for running a few legacy programs which
won't
run on W7-64bit. It's on a laptop running W7-PRO 64.

It's been ok for several years, but today it won't start. It puts up
the
usual little window saying "Starting Virtual Machine" and the
progress
marker starts moving to the right and when it's got about one
third of
the way across after about 40 seconds, the window closes - and that's
that. No error messages or anything. At the point when it closes, I
would expect it to say "Starting integration functions" - or
something
like that - but it doesn't.

I've re-booted numerous times to no avail. Malwarebytes doesn't find
anything amiss.

Anyone got any suggestions what to try next?

Go into Windows Update and see if you have KB2830477 installed.

If you have, remove it. And try VPC again.




That update is three years old, I would expect a more recent update to
be the possible problem.

Indeed. But I've uninstalled the other updates which have been installed
since Virtual XP last worked - to no avail!

dont do that..... your system file is likely corrupt. Go change it
manually. Its inside the windows/system folder. There is a backup that
is kept in the same folder with it somewhere, with a funny extension
name. sometimes even more than one of them. Its just a configuration
file that starts up the machine.... Sometimes they get corrupt. And
then, it don't work anymore... its not the update, so you need to leave
that alone...


So how do I go about restoring the system file?

  #26  
Old April 24th 17, 12:12 AM posted to alt.windows7.general
tesla sTinker
external usenet poster
 
Posts: 44
Default Virtual XP won't start

also if it does not improve, you may wish to check the SOFTWARE file
that is in the same place in the config folder. since your using a
software for virtual machine.... That file may of changed also.
The machine uses these files in the config folder when it powers up...
Just do same proceedure if you need to swap that one too..... right
clik, then replace....

On 4/23/2017 4:01 PM, tesla sTinker wrote:
should of emailed me...
I dont always hang on this group..

You know how to rename a file dont you?
Its that simple, you just have to find the old dated one that is the
backup of it. Then rename it after you have moved the other one and put
the backup in its place, so that its named exactly the same as the one
that is messed up. But copy that one to a folder that you make calling
it, old file system file.... Or something that you want to call it, so
if you need it again, you can just revert back to it in case you choose
poorly of which one is the good backup. There may be more than one
backup file of it. Depending on how much the machine has been used...


The path should be, C; Windows / System32 / config /
You will find it in there inside config folder...
The name should be SYSTEM in all capital letters.
The Type should be File
The Size should be about 17 mb, mine is little more than that....


Now, you might have a folder inside that config folder named RegBack.
Look in there also, to find another one of the same type file that says
on it, SYSTEM and check the size of it, and the Date. The Date modified
should be older, the one on the one that fires up the machine in the
config folder, should be the same date as now time, for its always
modified every time you start the machine....

so what you need to do, is make sure both those files are about the same
size. They should be. The one in the RegBack folder, and the one in the
config folder. Then, if they are, change them, but do not swap them.
What I did, was a I made a new folder in the config folder,
labeling it NewBkp... So that it was not the same as RegBack. And then I
took the SYSTEM file, and cut and paste it from the config folder, into
the NewBkp folder. That way, you know where it is. And, this will keep
you from renaming in it or having to rename it as long as you do all
this in its proper order.... This first of course. Then go in the
RegBack folder, and just copy that one into the config folder, and when
and if it ask you do you want to replace, say yes.
IF it asks... I mean if you copy instead of cut, it may still be there.
So it would ask this question. Now, there is the other option, under
your right clik of mouse, its called, restore previous versions. Instead
of doing all this... So just then find the folder config, in there is
the file named SYSTEM, And right clik on it, and you will see this
option in the menu, which is alot faster yes. But, as i said, you may
have more than one backup, and if you do, then you want to be picky
about dates,,,,,,


Then after all that, your done. Turn the machine off like you normally
do, and then restart it up again..... It should be more healthy if you
succeeded.

And if not, just undo the cut and paste copy. In restore previous
versions option, you dont have to move it at all, it will guide you to
do it..... It is easier and safer for those who do not know much about
computers.... We did it the manual way.... But both ways are the same.....

On 4/19/2017 3:27 PM, Roger Mills wrote:
On 19/04/2017 21:43, tesla sTinker wrote:


On 4/18/2017 10:34 AM, Roger Mills wrote:
On 18/04/2017 14:37, philo wrote:
On 04/17/2017 07:55 PM, Dave Doe wrote:
In article , ,
Roger Mills says...

I have a Virtual XP setup for running a few legacy programs which
won't
run on W7-64bit. It's on a laptop running W7-PRO 64.

It's been ok for several years, but today it won't start. It puts up
the
usual little window saying "Starting Virtual Machine" and the
progress
marker starts moving to the right and when it's got about one
third of
the way across after about 40 seconds, the window closes - and
that's
that. No error messages or anything. At the point when it closes, I
would expect it to say "Starting integration functions" - or
something
like that - but it doesn't.

I've re-booted numerous times to no avail. Malwarebytes doesn't find
anything amiss.

Anyone got any suggestions what to try next?

Go into Windows Update and see if you have KB2830477 installed.

If you have, remove it. And try VPC again.




That update is three years old, I would expect a more recent update to
be the possible problem.

Indeed. But I've uninstalled the other updates which have been
installed
since Virtual XP last worked - to no avail!
dont do that..... your system file is likely corrupt. Go change it
manually. Its inside the windows/system folder. There is a backup that
is kept in the same folder with it somewhere, with a funny extension
name. sometimes even more than one of them. Its just a configuration
file that starts up the machine.... Sometimes they get corrupt. And
then, it don't work anymore... its not the update, so you need to leave
that alone...


So how do I go about restoring the system file?

  #27  
Old April 27th 17, 03:57 AM posted to alt.windows7.general
Diesel
external usenet poster
 
Posts: 149
Default Virtual XP won't start

tesla sTinker
news alt.windows7.general, wrote:

should of emailed me...
I dont always hang on this group..

You know how to rename a file dont you?
Its that simple, you just have to find the old dated one that is
the backup of it. Then rename it after you have moved the other
one and put the backup in its place, so that its named exactly the
same as the one that is messed up. But copy that one to a folder
that you make calling it, old file system file.... Or something
that you want to call it, so if you need it again, you can just
revert back to it in case you choose poorly of which one is the
good backup. There may be more than one backup file of it.
Depending on how much the machine has been used...


I'm not sure he'll actually be able to do this, since it's not
booting at all; he'd need to be able to boot the virtual machine from
a usb stick and/or boot disk. I'd recommend bartpe for this.

He *should* be able to find a copy of the registry hive files (the
system file you referenced is one of them) in the system restore
folder, pending he hasn't got it disabled. Going by date stamps, I'd
resort to using the one that exists prior to his inability to boot.

Rather than copy one of the hive files over, I'd opt for copying ALL
of them over...This way, he won't have other, odd issues down the
road, if it turns out being a corrupted hive file. You want to keep
the hive files in sync if at all possible.

If he can set an option on vpc not to close the window when it
crashes out and post the resulting error message, it's possible more
detailed help could be provided to assist.

--
I would like to apologize for not having offended you yet.
Please be patient. I will get to you shortly.
 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 07:58 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright 2004-2017 PCbanter.
The comments are property of their posters.