Re: XP transfer wizard from 98 locks up

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

....

"TJ king" <TJking@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:84931054-580C-43CA-BA14-7F023E531F2B@xxxxxxxxxxxxxxxx
> My file transfer wizard from 98 to XP prof. keeps locking up. I have used
> multiple combinations and techniques. I have tried the across the network
> angle, then i tried saving to a folder on the destination computer and
> then
> using the wizard on the new XP PC. I have used the CD, Everything I do
> results in the XP PC locking up upon the attempt to apply the settings and
> files to the new XP. Is there a workaround for this. I'm desperate.
>


.

Relevant Pages

  • Re: XP Migration from 98 locks
    ... > My file transfer wizard from 98 to XP prof. keeps locking up. ... > used multiple combinations and techniques. ... What all is on your Windows 98 machine that you think you need on your ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Access 07: My query is making the back end database lock up
    ... settings for record-level locking, optimistic locking, and other ... I can have multiple machines open their own front-end instance of ... Can you work between the two open apps? ...
    (comp.databases.ms-access)
  • Re: fopen v. open and more
    ... thread-shared I/O buffers, ... often even without any locking. ... If multiple threads wish to write to the console, there has to be locking somewhere, either to a shared stream, or between multiple streams and a shared device. ...
    (comp.unix.programmer)
  • Re: BerkeleyDB locking question
    ... >> The simplest form of locking available in Berkeley DB is called ... >> Concurrent Data Store CDS. ... It allows single writer, multiple readers. ... DB uses per-machine IPC for locking. ...
    (comp.lang.perl.misc)
  • XP Migration from 98 locks
    ... My file transfer wizard from 98 to XP prof. keeps locking up. ... I have tried the across the network ... angle, then i tried saving to a folder on the destination computer and then ...
    (microsoft.public.windowsxp.setup_deployment)