G
Guest
Having locked myself out of 'Windows XP', after using the 'sysKey' which was
stored on a floppy disk - mainly due to distraction from stupid individuals.
Now because there is no recall for this option in windows, the only solution
is to re-format. In addition to this, because of some strange prior
installation there’s a problem with the root directory, if you try and
install a copy of MS-DOS independent of the package.
As a result, the ' c:\ drive' is not displaying, if I boot from the ' a:\
drive (floppy) ' and attempt to cd to the ' hard disk(c:\) '. Having also
downloaded the whole series of boot disks for ' WinXP '. ' , and not having
the drivers to install from MS - DOS to boot from the external CD - ROM drive
I brought with the laptop. The installation of ' XPOffice ' and ' XP Home
Edition ', I brought at great cost cannot now be installed with ease.
Is there any solution, someone can disclose that resolves this situation fast.
1. Booting into MS - DOS (with full command set - fdisk, diskpart etc.)
2. Detecting USB ports in MS - DOS (cd to a external drive or CD ROM)
3. Installing a copy of XP from the external Device.
Knowing for a fact that it’s possible to solve the same command line
problems in 'Linux redhat', with a few tweaks of the IRQ numbers. Although it
seems XP is near on impossible to administrate outside the package straight
into MS - DOS (if you are able to find a copy on the web).
In addition to this the old boot disks for windows 98, which were all
inclusive are now for some reason lock away, demanding validation to download.
Is this a bit too security conscious, or just a case of a bad installation
in the first instance.
Nothing Lost, just the time constraints on the re-installation. Not everyone
finds a laptop with internal cd-rom affordable, and to be honest not that
essential as most situations are attainable in command line, with more help
towards the topic.
With this in mind, the format of the help file is also confusing, and the
documentation on '.BAT' - bash files seems incomplete without much if any
referencing. Surely there could be a set of automotive solutions to common
problems of installation and administration.
stored on a floppy disk - mainly due to distraction from stupid individuals.
Now because there is no recall for this option in windows, the only solution
is to re-format. In addition to this, because of some strange prior
installation there’s a problem with the root directory, if you try and
install a copy of MS-DOS independent of the package.
As a result, the ' c:\ drive' is not displaying, if I boot from the ' a:\
drive (floppy) ' and attempt to cd to the ' hard disk(c:\) '. Having also
downloaded the whole series of boot disks for ' WinXP '. ' , and not having
the drivers to install from MS - DOS to boot from the external CD - ROM drive
I brought with the laptop. The installation of ' XPOffice ' and ' XP Home
Edition ', I brought at great cost cannot now be installed with ease.
Is there any solution, someone can disclose that resolves this situation fast.
1. Booting into MS - DOS (with full command set - fdisk, diskpart etc.)
2. Detecting USB ports in MS - DOS (cd to a external drive or CD ROM)
3. Installing a copy of XP from the external Device.
Knowing for a fact that it’s possible to solve the same command line
problems in 'Linux redhat', with a few tweaks of the IRQ numbers. Although it
seems XP is near on impossible to administrate outside the package straight
into MS - DOS (if you are able to find a copy on the web).
In addition to this the old boot disks for windows 98, which were all
inclusive are now for some reason lock away, demanding validation to download.
Is this a bit too security conscious, or just a case of a bad installation
in the first instance.
Nothing Lost, just the time constraints on the re-installation. Not everyone
finds a laptop with internal cd-rom affordable, and to be honest not that
essential as most situations are attainable in command line, with more help
towards the topic.
With this in mind, the format of the help file is also confusing, and the
documentation on '.BAT' - bash files seems incomplete without much if any
referencing. Surely there could be a set of automotive solutions to common
problems of installation and administration.