Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Launch windows XP from a DOS prompt?
- Thread starter abelxcain
- Start date
gpalmer711
IS-IT--Management
There is no way of doing this. Windows XP no longer uses true Dos. Therefor you could not load Dos 6.2 for example and then use a command to load windows XP.
Greg Palmer
Freeware Utilities for Windows Administrators.
Greg Palmer
Freeware Utilities for Windows Administrators.
- Thread starter
- #3
Greg thank you for your reply. My problem is in updating the firmware in an NEC CDRW. I finally found what I needed: it runs a batch file but only from a floopy. For it must update prior to loading win xp. Yet once it has been updated the system stays in the DOS prompt. If i turn the machine off, reboot, I then lose the update. Surely there is a backdoor or something that will allow me to enter into win xp from the DOS prompt, even thouhg I could not find it in the directories. However, I am not sure how to use the switches to expose the hidden files in the windows directory. I tried that but got bad command. I apparently typed the switch wrong.
I am sure that there is someone out there who knows how to work around this DOS prompt problem. I do understand what you are saying and I am equally sure that you are correct as far as conventional means.
Shane
I am sure that there is someone out there who knows how to work around this DOS prompt problem. I do understand what you are saying and I am equally sure that you are correct as far as conventional means.
Shane
If you are in a true DOS prompt, then you are only able to view FAT partitions. Most XP users use the NTFS system and your DOS session would not allow you to view those partitions.
I do not understand why this update must use two seperate operating systems to update the firmware? Why not just put the file in the autoexec.bat, because i believe that WinXP still executes that before it loads.
Computer/Network Technician
CCNA
I do not understand why this update must use two seperate operating systems to update the firmware? Why not just put the file in the autoexec.bat, because i believe that WinXP still executes that before it loads.
Computer/Network Technician
CCNA
- Thread starter
- #8
THANKS GUYS, Maybe I just do not have the brains <smile>. Here is the read me txt. It is actually from the 1.05 version but after unpacking the 1.06a version it gives the exact same read me. The main difference at least in operation is that 106 runs a batch file. So that you do not have to make the startup disk with the autoexec, etc... files. The batch file does all the copying of the needed files and then upgards the firmware but then leaves you in true DOS. I amy be able to run it from the CMD prompt within the win enviroment but it seems that the read me says that it won't work to good that way.
Usage procedure for flash utility for NR-7700A
0. Creating a startup disk
Do a floppy disk format and system transfer.
Copy the all files (autoexec.bat,utilities and HEX File) to a floppy disk.
Start up using this floppy disk.
1. Executing the utility
After connecting to PC the drive which rewrites a firmware,
PC is started using the created starting disk.
DOS starts and a utility operates.
2. F/W update
Automatic recognition is executed for the drive
with the necessity of rewriting a firmware, and a firmware is updated.
Finally please switch off power momentarily and then restart the system. The updated F/W is started.
3. Recommended environment
We recommend running under the following environment.
o Startup using floppy disk drive
Use of the hard disk drive is possible, but we recommend starting up on the floppy disk drive because the IDE hard disk drive is using the same bus.
o Use of MS-DOS ver 6.2 or higher
It should be possible to use this software with a cmpatible DOS, but because the system has been built assuming MS-DOS ver 6.2, we recommend using this version of DOS.
o Don't install device drivers (CONFIG.SYS unnecessary)
The utility does not require any device drivers. If device drivers are installed, operation of the utility could become unstable. In particular, be sure to eliminate any disk caching device drivers (SMARTDRV, etc.).
Note:
Busy LED
There are cases where the drive BUSY lamp continues to blink whether or not there are accesses. The conditions for this are the following.
o There is a problem with the data in the flash memory.
o The data in the flash memory has been read. (The blinking stops if the system is restarted.)
o The data in the flash memory has been overwritten. (The blinking stops if the system is restarted.)
Usage procedure for flash utility for NR-7700A
0. Creating a startup disk
Do a floppy disk format and system transfer.
Copy the all files (autoexec.bat,utilities and HEX File) to a floppy disk.
Start up using this floppy disk.
1. Executing the utility
After connecting to PC the drive which rewrites a firmware,
PC is started using the created starting disk.
DOS starts and a utility operates.
2. F/W update
Automatic recognition is executed for the drive
with the necessity of rewriting a firmware, and a firmware is updated.
Finally please switch off power momentarily and then restart the system. The updated F/W is started.
3. Recommended environment
We recommend running under the following environment.
o Startup using floppy disk drive
Use of the hard disk drive is possible, but we recommend starting up on the floppy disk drive because the IDE hard disk drive is using the same bus.
o Use of MS-DOS ver 6.2 or higher
It should be possible to use this software with a cmpatible DOS, but because the system has been built assuming MS-DOS ver 6.2, we recommend using this version of DOS.
o Don't install device drivers (CONFIG.SYS unnecessary)
The utility does not require any device drivers. If device drivers are installed, operation of the utility could become unstable. In particular, be sure to eliminate any disk caching device drivers (SMARTDRV, etc.).
Note:
Busy LED
There are cases where the drive BUSY lamp continues to blink whether or not there are accesses. The conditions for this are the following.
o There is a problem with the data in the flash memory.
o The data in the flash memory has been read. (The blinking stops if the system is restarted.)
o The data in the flash memory has been overwritten. (The blinking stops if the system is restarted.)
Do not run it under CMD. One never messes with a flash of any firmware.
. Insert a blank floppy disk. Go to my computer, right-click the A: drive, and select format. Select the box at the bottom to create an MS-DOS bootable disk.
. When finished, copy the unpacked contents of your firmware download to the disk.
. Restart, the computer, and check that the BIOS boot order of devices is set to boot from floppy disk first.
. The system should boot from the floppy, and the firmware flash should happen. Do not interrupt.
. When completely done, remove the floppy.
. Restart the computer, stopping first to reset the BIOS
boot order back to its original settings.
. Insert a blank floppy disk. Go to my computer, right-click the A: drive, and select format. Select the box at the bottom to create an MS-DOS bootable disk.
. When finished, copy the unpacked contents of your firmware download to the disk.
. Restart, the computer, and check that the BIOS boot order of devices is set to boot from floppy disk first.
. The system should boot from the floppy, and the firmware flash should happen. Do not interrupt.
. When completely done, remove the floppy.
. Restart the computer, stopping first to reset the BIOS
boot order back to its original settings.
- Status