5308-64: Serious file I/O issue?

  • Thread starter Thread starter Vista Tester
  • Start date Start date
V

Vista Tester

I'm finding serious problems (system lock/crash) trying to xfer files from a
shared folder across a network. So far, it only seems to be a problem in
the 64-bit version of Vista.

Try placing a 50MB file in the Public folder on a 64bit system. Make sure
sharing is turned on. Then, go to another machine and try to copy the file
through the network. If that works, then try it with a 1G file.

There are a LOT of variables here, so before I spend much more time trying
to diagnose, I wanted to find out if others had noticed any issues.
 
OK, I've tried doing this with a Futurama video (I used Movie Maker to make
it into a Pocket PC optimised file) so that made it 63MB which is
thereabouts OK. That works fine.

I tried zipping my entire Counter-Strike directory which amazingly comes to
1.02GB and that also works fine... try submitting this as a bug :o)

--
Zack Whittaker
» ZackNET Enterprises: www.zacknet.co.uk
» MSBlog on ResDev: www.msblog.org
» Vista Knowledge Base: www.vistabase.co.uk
» This mailing is provided "as is" with no warranties, and confers no
rights. All opinions expressed are those of myself unless stated so, and not
of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared
that up!


--- Original message follows ---
 
Sorry to hear that :) Sounds like I've got a bit more work ahead of me.

What was the system configuration on the other machine?
 
Well, I had two machines:

Machine 1: \\VISTACHROME
256MB RAM, AMD 1900+ 32-bit processor
30GB hard disk space, Glass enabled.
System Performance Rating: 2

Machine 2: \\VISTAPLATINUM
1GB RAM, Dual Core AMD 64
230GB hard disk space, Glass enabled.
System Performance Rating: 4

Transported files from \\VISTACHROME to \\VISTAPLATINUM over the network,
with Windows Server 2003 R2 server in place.

--
Zack Whittaker
Windows Server 2003 R2 Mentor
» ZackNET Enterprises: www.zacknet.co.uk
» MSBlog on ResDev: www.msblog.org
» Vista Knowledge Base: www.vistabase.co.uk
» This mailing is provided "as is" with no warranties, and confers no
rights. All opinions expressed are those of myself unless stated so, and not
of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared
that up!


--- Original message follows ---
 
I'm not sure about the exact nature of the problem you are seeing while
transferring large files. If you are still seeing problems and can elaborate
on the problem, we could diagonise the issue.

* Is transfer failing with any particular error code ?
* Is the system blue-screening while transferring data ?
* Is the system taking a unusually long time to tranfer fails (which might
manifest itself as a system lock/hang) ?

Also, what OS are the server and client running ?

If you can get a network capture (using netmon/ethereal), that might be a
good start to investigate this.

Thanks ~
Prashanth

Vista Remote File Systems
 
Here's some more detail:

1) The same problem occurs when running under safe mode wi networking
2) I'm mapping a network drive to the remote computer (drive S:)
3) I copy the file from my 5308-64 machine to drive S (XP-pro machine)
4) "Calculating time remaining" box pops up - and never gets to next step
5) The network connection drops (?!) Drive S no longer exists
6) There doesn't seem to be a corresponding error message in the log,
nor is there an error message on screen
7) The only way to recover is to power the machine off

The error sounds real familiar. I seem to remember something about the
drive mappings disappearing during file copies back in Win 98. I dunno if
it's related...
 
1.02GB and that also works fine... try submitting this as a bug :o)

Zack - I'm not sure that I can. I'm one of them beta-tester wannabies so I
don't have access to the connect site...
 
Ahh course you can! Download the Beta Client here:
http://go.microsoft.com/fwlink/?LinkId=43655 and when you go to submit,
simply click the button that says "File this report anonymously".

But the question asks... how did you get the copy of 5308 if you're not a
tester? ;o)

--
Zack Whittaker
Windows Server 2003 R2 Mentor
» ZackNET Enterprises: www.zacknet.co.uk
» MSBlog on ResDev: www.msblog.org
» Vista Knowledge Base: www.vistabase.co.uk
» This mailing is provided "as is" with no warranties, and confers no
rights. All opinions expressed are those of myself unless stated so, and not
of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared
that up!


--- Original message follows ---
 
Gotcha.

I got 5308 through MSDN

Zack Whittaker said:
Ahh course you can! Download the Beta Client here:
http://go.microsoft.com/fwlink/?LinkId=43655 and when you go to submit,
simply click the button that says "File this report anonymously".

But the question asks... how did you get the copy of 5308 if you're not a
tester? ;o)

--
Zack Whittaker
Windows Server 2003 R2 Mentor
» ZackNET Enterprises: www.zacknet.co.uk
» MSBlog on ResDev: www.msblog.org
» Vista Knowledge Base: www.vistabase.co.uk
» This mailing is provided "as is" with no warranties, and confers no
rights. All opinions expressed are those of myself unless stated so, and
not of my employer, best friend, Ghandi, my mother or my cat. Glad we
cleared that up!


--- Original message follows ---
Click to expand...
 
Oooh sorry, getting 5308 and 5342 mixed up... if you weren't a techy tester
and got your hands on 5342, I'd be worried! :oP

--
Zack Whittaker
Windows Server 2003 R2 Mentor
» ZackNET Enterprises: www.zacknet.co.uk
» MSBlog on ResDev: www.msblog.org
» Vista Knowledge Base: www.vistabase.co.uk
» This mailing is provided "as is" with no warranties, and confers no
rights. All opinions expressed are those of myself unless stated so, and not
of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared
that up!


--- Original message follows ---
 
Yup. I set things up to do a Kernel Dump on crash, but the mapped
drive/folder sharing lockup doesn't cause a managed crash. It just locks
the system solid.

Since I noted these issues, there has been at least one (or two?) interim
release of a new beta. Does it make sense to continue to debug an older
release when the code we might be addressing could have been changed?
 
Back
Top