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. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Noodlebaking with Regedit!
I install exactly the same Ghost image of a system core onto two machines. I
have a Run-Once.bat file to create the registry from a REG file at first boot after restoring the image, with an Autoexec line REGEDIT /C W98_CORE.REG In one machine this creates SYSTEM.DAT and USER.DAT, in the other it doesn't! Why? In both cases, REGEDIT.EXE reports 100% success. All other file accesses appear to work as anyone with twenty years of DOS experience would expect. I searched for SYSTEM.DAT using ATTRIB /S SYSTEM.* in the root of C because that WILL find it, absolutely, if it's anywhere on that drive. All it found was SYSTEM.INI and SYSTEM.DRV. I wish I had oodles of cash prizes to give away because this one really IS a three-pipe noodlebaker. Does anyone know the answer? |
#2
|
|||
|
|||
Noodlebaking with Regedit!
Lostgallifreyan wrote in
: I install exactly the same Ghost image of a system core onto two machines. I have a Run-Once.bat file to create the registry from a REG file at first boot after restoring the image, with an Autoexec line REGEDIT /C W98_CORE.REG In one machine this creates SYSTEM.DAT and USER.DAT, in the other it doesn't! Why? In both cases, REGEDIT.EXE reports 100% success. All other file accesses appear to work as anyone with twenty years of DOS experience would expect. I searched for SYSTEM.DAT using ATTRIB /S SYSTEM.* in the root of C because that WILL find it, absolutely, if it's anywhere on that drive. All it found was SYSTEM.INI and SYSTEM.DRV. I wish I had oodles of cash prizes to give away because this one really IS a three-pipe noodlebaker. Does anyone know the answer? Ok, I got it. It's REGEDIT itself, it will hunt for a SYSTEM.DAT and find it, even if it can't find one till it reaches the last logical drive on the last disk (of three in this case) in the system, so long as it's also in a dir called WINDOWS in the root of that drive! Never mind envvar %WINDIR% or whatever is in MSDOS.SYS, it utterly ignores that if it checks it at all, and persists in using some obscure backup SYSTEM.DAT file it shouldn't even know about. I still don't know why it should do this, or if there is any way to over-ride this except by forcing a total absence of _:\WINDOWS\SYSTEM.DAT where _ is any drive whatsover. While it's possible to tell REGEDIT explicitly where SYSTEM.DAT is to get an export to REG file, I don't know if the same can be done when creating a new registry, or adding entries to an existing DAT file. |
#3
|
|||
|
|||
Noodlebaking with Regedit!
Lostgallifreyan wrote in
: I wish I had oodles of cash prizes to give away because this one really IS a three-pipe noodlebaker. Does anyone know the answer? Hmm, three hours, if not three pipes. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
need help with REGEDIT | Jack | General | 6 | January 22nd 05 03:55 AM |
Cannot run regedit | Jeremiah | General | 2 | January 1st 05 07:08 PM |
cant run regedit | General | 4 | July 28th 04 11:23 PM | |
REGEDIT | rr@[email protected] | General | 1 | July 23rd 04 07:58 PM |
Regedit won't run | Alan C | General | 2 | June 6th 04 02:09 AM |