| Topic: ? about placing a Network Boot disk on CD, Password wants to save to CD... | < Next Oldest | Next Newest > |
|
| Post Number: 1
|
jawakotb 
Group: Members
Posts: 11
Joined: Jan. 2004
|
 |
Posted on: Jan. 23 2004,14:14 |
|
   |
With the WindowsXP created boot disk creator, I have created a network bootdisk that loads up the correct NIC drives and then tries to attach to my network server/share. The System.ini has all the correct statements in it, and it works just fine from Floppy. But when I create the IMG file of that floppy and then using EasyBoot place it on the CD it works with on flaw. After it asks for the USERNAME and password, the system states it cannot write to the CD. (Which it is correct in stating.) My question is, does anybody know how to stop the MS files from trying to create the password (*.PWL) file in the first place? (Perhaps a switch in the system.ini file?)
Thanks for the help all!
|
 |
|
|
| Post Number: 2
|
martinx
Group: Members
Posts: 88
Joined: Nov. 2003
|
|
Posted on: Jan. 25 2004,09:16 |
|
 |
The emulated floppy drive created by EasyBoot is read-only, you can resolve this kind of problem by using third-party tools such as Boot CD Wizard.
|
|
|
|
| Post Number: 3
|
Hannes
Group: Members
Posts: 68
Joined: Dec. 2003
|
|
Posted on: Jan. 25 2004,18:03 |
|
|
One other thing you could do is to boot from the original floppy one and allow it to create the PWD file. After that, create the IMG file and your image will then have the PWD file on it already.
Hannes
|
|
|
|
| Post Number: 4
|
Jawakotb
Unregistered
|
|
Posted on: Jan. 26 2004,10:07 |
|
|
The floppy diskette already does have the pwl file there, but for unknown reasons the #### MS files wish to re-write the pwl file again. (I was thinking the same thing...hehe)
Is there any type of "switch" or statement that can be placed in the protocol.ini or system.ini of the floppy diskette to which then passwords will NOT be saved? MS Technet KB is not very helpfull in my quest either.
|
|
|
|
| Post Number: 5
|
Hannes
Group: Members
Posts: 68
Joined: Dec. 2003
|
|
Posted on: Jan. 26 2004,11:27 |
|
|
I'll have to experiment with that if I get a chance at some point. The only other thing I could think of would be this:
You could create a RAMDISK and then have all your files copied to the ramdisk. This way it would be writable and the problem would be solved!
Hannes
|
|
|
|
| Post Number: 6
|
jawakotb
Group: Members
Posts: 11
Joined: Jan. 2004
|
|
Posted on: Jan. 27 2004,10:29 |
|
|
RAMDISK,  !
Do you have a link to this Program so I may look into this as an option? I have found RamDisk for 9x/NT/W2k/XP but not dos...
Thanks!
|
|
|
|
| Post Number: 7
|
Hannes
Group: Members
Posts: 68
Joined: Dec. 2003
|
|
Posted on: Jan. 27 2004,19:51 |
|
|
There is one included with DOS called RAMDRIVE.SYS. If you need more functionality just search on "Ramdisk DOS" and you should find plenty of them on the internet.
Let me know if you need any more help with this!
Hannes
|
|
|
|
| Post Number: 8
|
ntsc
Group: Members
Posts: 1
Joined: Jan. 2004
|
|
Posted on: Jan. 29 2004,17:55 |
|
|
Pleased someone else is having the same problem !!!
Considered a ramdrive - found one on the Net which allows you to assign a fixed drive letter as well
I am assuming that I will need to attrib some of the files copied to the Ramdrive as won't they be read only after being originally copied to the CDROM, to allow them to be altered during the boot process ?.
Most of the systems I will be trying to use this on will have the CDROM as drive D - is their anyway of passing back the assigned CDROM drive letter in case I encounter a system with Multiple Partitions and therefore the CDROM drive letter won't be D ? - so that the copy or xcopy commands will be able to copy the files from the CDROM to the ramdrive.
Hopefully I'll get chance to do a test over the next week - so I'll report back if anyone is interested
|
|
|
|
|
|
