Hi, I posted this question a month ago but had to go to London and didn't resolve the issue, but I hope you will bare with me on this one. Over this last month I have been trying, but no solution. I have a new AMD64 laptop from TPG, but TPG are very secretive about the contents of the box and refuse to discuss Linux (though it makes no sense to sell a 64 bit machine with XP ! ) However, XP tells me that the screen resolution is 1280 x 800 at 60 Hz and the adapter is an SiS, model: 651_661FX_741_760_760GX_M661FX_M661MX_M741_M on PCI bus 1, device 0, function 0 64 MB of the main RAM appears to be used for the video The problem is that 1. SuSE 9.1 install starts properly (full screen, good quality graphics with menus, edit boxes etc. 2. internet connects and tests correctly 3. downloads latest SuSE updates automatically 4. lots of software appears to be correctly installed 5. system reboots from hard disk 6. requests, and achieves, setup for root and for a user 7. system reboots and requests loggin 8. system then says that it cannot determine monitor characters, and asks if I want to configure manually? Note: up until this point the system has had zero problem with displaying windows, graphics etc. Something in the initial SuSE code "gets it right". 8.(cont) If I configure manually or not the system then jumps into some ridiculous mode of 0 x 0 pixels. Thus, it appears that the SuSE programmer requests the screen dimensions, and receives 0 x 0 and fails to check the values, and simply attempts to use 0 x 0, thereby sending the system into convoltions. I can only switch off the electricty at this point. When I try to reboot from the hard disc everything goes well until the system gets to the loggin screen whereby the screen promptly jumps into convoltions again. Booting with F2 setting the screen dimensions does not help. How can the initial part of the SuSE code get the screen perfectly correct while the latter part stuffs it up? Any ideas on how to interrupt the boot process and set the screen parameters? Any ideas on how to get SuSE to fix this bug? Regards, Colin