Liverpool FC Forum

by **Woollyback** » Wed Feb 14, 2007 4:06 pm

whenever i plug my ipod into my computer it just gives me a dialogue box saying "windows - no disk" and 3 buttons - cancel, try again, and continue - none of which actually do anything other than bring the dialogue box up again. when this happens itunes freezes and won't respond

it was working fine last night, this has just happened today

any idea's what the feck's up with it?

by **Leonmc0708** » Wed Feb 14, 2007 4:52 pm

Could be the wrong state:

Page state, commonly referred to as view state, is persisted in a hidden form field, by default. When a page is being rendered, any programmatic changes to a control's state is saved to the page's overall view state. During the rendering stage, this view state is serialized into a base-64 encoded hidden form field and sent down to the client's browser. On postback, the view state data is sent back to the web server, where it is deserialized and returned to the appropriate Web controls in control hierarchy so that they may re-establish their state as it was prior to the postback.

View state provides a slick way to remember state in a stateless client-server model and it happens underneath the covers without any extra effort from page developers. The downside of view state, however, is that in certain situations the view state can grow to be exceedingly large. A large view state requires a longer page download time since it bloats the total web page size and also affects the postback time, since the entire view state content must be posted back to the web server along with the other form fields.

by **red37** » Wed Feb 14, 2007 5:12 pm

Leonmc0708 wrote:Could be the wrong state:

Page state, commonly referred to as view state, is persisted in a hidden form field, by default. When a page is being rendered, any programmatic changes to a control's state is saved to the page's overall view state. During the rendering stage, this view state is serialized into a base-64 encoded hidden form field and sent down to the client's browser. On postback, the view state data is sent back to the web server, where it is deserialized and returned to the appropriate Web controls in control hierarchy so that they may re-establish their state as it was prior to the postback.

View state provides a slick way to remember state in a stateless client-server model and it happens underneath the covers without any extra effort from page developers. The downside of view state, however, is that in certain situations the view state can grow to be exceedingly large. A large view state requires a longer page download time since it bloats the total web page size and also affects the postback time, since the entire view state content must be posted back to the web server along with the other form fields.

i was just going to say the same thing Leon.......

wtf!

by **Woollyback** » Wed Feb 14, 2007 5:30 pm

Leonmc0708 wrote:Could be the wrong state:

Page state, commonly referred to as view state, is persisted in a hidden form field, by default. When a page is being rendered, any programmatic changes to a control's state is saved to the page's overall view state. During the rendering stage, this view state is serialized into a base-64 encoded hidden form field and sent down to the client's browser. On postback, the view state data is sent back to the web server, where it is deserialized and returned to the appropriate Web controls in control hierarchy so that they may re-establish their state as it was prior to the postback.

View state provides a slick way to remember state in a stateless client-server model and it happens underneath the covers without any extra effort from page developers. The downside of view state, however, is that in certain situations the view state can grow to be exceedingly large. A large view state requires a longer page download time since it bloats the total web page size and also affects the postback time, since the entire view state content must be posted back to the web server along with the other form fields.

don't make me come over to liverpool and kick yer head in leon :angry:

by **Woollyback** » Wed Feb 14, 2007 5:37 pm

leon you're a lucky boy, i've got it working again - excusing you from a ferocious beating

by **Leonmc0708** » Wed Feb 14, 2007 5:50 pm

Woollyback wrote:leon you're a lucky boy, i've got it working again - excusing you from a ferocious beating

Listen sausage, you got it working due to my adice - make no mistake abotu that.

by **SouthCoastShankly** » Wed Feb 14, 2007 6:03 pm

I was gunna say that my friend had the same problem. He found that reinstalling both Quicktime and Itunes did the trick.

by **anfieldadorer** » Wed Feb 14, 2007 6:42 pm

Woollyback wrote:leon you're a lucky boy, i've got it working again - excusing you from a ferocious beating

argh, too late, i was typing a full A4 solution :veryangry

by **Woollyback** » Wed Feb 14, 2007 10:54 pm

turns out i just used a different usb port and bingo, robert is your mother's brother :buttrock

Liverpool FC Forum

Ipod help

Who is online