[Poetic]

kay well there have been some issues with my laptop T_T, like my sound card and graphics card are not being read/recognized by my laptop after I reformatted. Examples are... I can run anime on my computer but theres no sound and my built in speakers arent working. As for Graphics I cant play any games ( H ones too T_T) Any suggestions on how to fix this issue?

[saufi89]

from my opinion,u should know what graphic card and sound card on your laptop..then u can format your laptop..if u know,youre lucky because u can search it on internet...download its driver file..thats for sure...there are tons of website that allow people to download the driver files to make your graphic and sound card to work...(its normal your graphic and sound card not recognised by os becoz they need driver file to work!)

[xibo]

huh?! the software emulation mode should offer enough graphics power to run h-games, at least visual novel ones ( the video sequences could be stepping though )

either way, get a linux boot disk, boot with it, and after you logged in type lspci, then you should get something like:

magi ~ # lspci
00:00.0 Host bridge: Intel Corporation DRAM Controller (rev 02)
00:01.0 PCI bridge: Intel Corporation PCI Express Root Port (rev 02)
00:03.0 Communication controller: Intel Corporation MEI Controller (rev 02)
00:19.0 Ethernet controller: Intel Corporation 82566DC-2 Gigabit Network Connection (rev 02)
00:1a.0 USB Controller: Intel Corporation USB UHCI Controller #4 (rev 02)
00:1a.1 USB Controller: Intel Corporation USB UHCI Controller #5 (rev 02)
00:1a.2 USB Controller: Intel Corporation USB UHCI Controller #6 (rev 02)
00:1a.7 USB Controller: Intel Corporation USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation PCI Express Port 4 (rev 02)
00:1c.4 PCI bridge: Intel Corporation PCI Express Port 5 (rev 02)
00:1d.0 USB Controller: Intel Corporation USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation USB UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92)
00:1f.0 ISA bridge: Intel Corporation LPC Interface Controller (rev 02)
00:1f.2 RAID bus controller: Intel Corporation 82801 SATA RAID Controller (rev 02)
00:1f.3 SMBus: Intel Corporation SMBus Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation G80 [GeForce 8800 GTX] (rev a2)
03:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6101 single-port PATA133 interface (rev b1)
04:00.0 PCI bridge: Texas Instruments XIO2000(A)/XIO2200(A) PCI Express-to-PCI Bridge (rev 03)
05:00.0 Serial controller: NetMos Technology PCI 9835 Multi-I/O Controller (rev 01)

Then the write up the names of the hardware somewhere and reboot to windows and websearch for the corresponding drivers
if you have a vFAT ( vfat is like fat32 but allows file names with more then 8 characters and (multiple) extentions with more then 3 characters ; windows 95 & company fdisk call it FAT32 nevertheless -.- ) partition you can save the effort of writing it up per hand by "redirecting" lspci's default output into a file on that vFAT partition

EDIT: daaa i m writing too much T_T
here we go >_<

Spoiler for finding/mounting vFAT partitions and redirecting the output to a file on them

first off, if you have a halfway new laptop the HDD will be /dev/sd-something ( serial ata or scsi ), if it s old, it s /dev/hd-something ( parallel ata )
to get a list of all attached sd/hd devices use dmesg ( prints kernel messages ) and "pipe" ( vertical line on the same key where backslash is on english layout ) the output into grep ( regular expression parser )

magi ~ # dmesg | grep sd
[    0.000000] Command line: root=/dev/sda5 vga=0x307
[    0.000000] Kernel command line: root=/dev/sda5 vga=0x307
[    1.512802] Driver 'sd' needs updating - please use bus_type methods
[    4.742833] sd 0:0:0:0: [sda] 1465149168 512-byte hardware sectors (750156 MB)
[    4.745606] sd 0:0:0:0: [sda] Write Protect is off
[    4.748360] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    4.748377] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    4.751269] sd 0:0:0:0: [sda] 1465149168 512-byte hardware sectors (750156 MB)
[    4.754173] sd 0:0:0:0: [sda] Write Protect is off
[    4.757044] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    4.757064] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    4.760015]  sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
[    4.801393] sd 0:0:0:0: [sda] Attached SCSI disk
[    4.804596] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    4.810770] sd 4:0:0:0: [sdb] 1465149168 512-byte hardware sectors (750156 MB)
[    4.814007] sd 4:0:0:0: [sdb] Write Protect is off
[    4.817009] sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    4.817025] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    4.820125] sd 4:0:0:0: [sdb] 1465149168 512-byte hardware sectors (750156 MB)
[    4.823248] sd 4:0:0:0: [sdb] Write Protect is off
[    4.826340] sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    4.826357] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    4.829492]  sdb: sdb1
[    4.838608] sd 4:0:0:0: [sdb] Attached SCSI disk
[    4.842007] sd 4:0:0:0: Attached scsi generic sg1 type 0
[   13.000490] sd 8:0:0:0: [sdc] 1003520 512-byte hardware sectors (514 MB)
[   13.001484] sd 8:0:0:0: [sdc] Write Protect is off
[   13.001484] sd 8:0:0:0: [sdc] Mode Sense: 00 00 00 00
[   13.001484] sd 8:0:0:0: [sdc] Assuming drive cache: write through
[   13.005008] sd 8:0:0:0: [sdc] 1003520 512-byte hardware sectors (514 MB)
[   13.006485] sd 8:0:0:0: [sdc] Write Protect is off
[   13.006485] sd 8:0:0:0: [sdc] Mode Sense: 00 00 00 00
[   13.006485] sd 8:0:0:0: [sdc] Assuming drive cache: write through
[   13.006485]  sdc: sdc1
[   13.060381] sd 8:0:0:0: [sdc] Attached SCSI removable disk
[   13.060415] sd 8:0:0:0: Attached scsi generic sg3 type 0
[   13.619569] EXT3 FS on sda5, internal journal
[   13.835707] EXT4 FS on sdb1, internal journal
[   35.050474] Adding 2096440k swap on /dev/sda6.  Priority:-1 extents:1 across:2096440k

something like
[ 4.760015] sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
means the first (in detection order) serial ata device ( sda , second is sdb, ... ) has 5 partitions ( sda1 , sda2, sda3, sda5 and sda6 - sda4 is only virtual, divided into two partitions as displayed by the content of the greater and smaller tags behind it )
[ 4.829492] sdb: sdb1
means the serial ata device has only one partition: sdb1

you can of cause use fdisk or so to find out what partition is vFAT, but via brute force it also works ( and doesn t trash your partition table if you press the wrong series of keys )

magi ~ # mkdir /fatpartition
magi ~ # mount -t vfat -o rw /dev/sda1 /fatpartition

if that worked you can access the data from /dev/sda via the /fatpartition directory. otherwise try the next partition...

magi ~ # mount -t vfat -o rw /dev/sda2 /fatpartition
magi ~ # mount -t vfat -o rw /dev/sda3 /fatpartition
.
.
.
magi ~ # mount -t vfat -o rw /dev/sdb1 /fatpartition
.
.
.

additionally you can use an usb stick, because usb sticks are also always formated with vfat, and gets recognized by the kernel within 5 seconds. see the ( end of the ) kernel output with dmesg again:

magi ~ # dmesg
.
.
.
[ 4089.895028] usb 1-3: new high speed USB device using ehci_hcd and address 7
[ 4090.010943] usb 1-3: configuration #1 chosen from 1 choice
[ 4090.011485] scsi9 : SCSI emulation for USB Mass Storage devices
[ 4090.011686] usb-storage: device found at 7
[ 4090.011686] usb-storage: waiting for device to settle before scanning
[ 4090.011485] usb 1-3: New USB device found, idVendor=1307, idProduct=0163
[ 4090.011485] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4090.011485] usb 1-3: Product: USB Mass Storage Device
[ 4090.011485] usb 1-3: Manufacturer: USBest Technology
[ 4090.011485] usb 1-3: SerialNumber: 07051800006689
[ 4095.011397] scsi 9:0:0:0: Direct-Access     Ut163    USB2FlashStorage 0.00 PQ: 0 ANSI: 2
[ 4095.013110] sd 9:0:0:0: [sdc] 1003520 512-byte hardware sectors (514 MB)
[ 4095.013448] sd 9:0:0:0: [sdc] Write Protect is off
[ 4095.013448] sd 9:0:0:0: [sdc] Mode Sense: 00 00 00 00
[ 4095.013448] sd 9:0:0:0: [sdc] Assuming drive cache: write through
[ 4095.016458] sd 9:0:0:0: [sdc] 1003520 512-byte hardware sectors (514 MB)
[ 4095.017084] sd 9:0:0:0: [sdc] Write Protect is off
[ 4095.017088] sd 9:0:0:0: [sdc] Mode Sense: 00 00 00 00
[ 4095.017094] sd 9:0:0:0: [sdc] Assuming drive cache: write through
[ 4095.017097]  sdc: sdc1
[ 4095.071396] sd 9:0:0:0: [sdc] Attached SCSI removable disk
[ 4095.071396] sd 9:0:0:0: Attached scsi generic sg3 type 0
[ 4095.071396] usb-storage: device scan complete

that tells you that the usb stick is sdc, and it s partition mount point sdc1

magi ~ # mkdir /usbstick
magi ~ # mount -t vfat -o rw /dev/sdc1 /usbstick

to create a directory called /usbstick and mount the usb stick inside of it

then , to save the output of lscpi into a text file, type

magi ~ # lspci > /usbstick/lspci.txt
magi ~ # umount /usbstick

the thing right of lspci is the greater character. you need to unmount the partition before you pull out the usb-stick in order to avoid filsystem corruption ( the linux kernel buffers the data to avoid file fragmentation but at the point a partition needs to be released all remaining transactions are handled )

magi ~ # reboot

access the usb stick or HDD partition via windows and open the lspci.txt directly uppon it with WORDPAD - it will NOT work propperly with notepad.

[Macho Moron]

One question : Vista or XP?

If it's Vista, you deserve to be punished.

Quote:

And finally, this could also be caused by a driver problem. If you go to
Start:Run and type "dxdiag" in the command box (not including the double
quotes), then press return, you can run Microsoft DirectX Diagnostic.
There is a sound test in there. If the sound test runs, and no software
errors are reported, and yet you aren't hearing any sound, then it could
be there is a wiring problem. (Click "Test DirectSound" button.)

http://www.mysuperpc.com/build/dxdiag_tests_5_sm.gif

It can even be a case, where the user has accidentally clicked a "Mute"
box in the Mixer control panel, which is causing the sound volume to
be zero.

So try a few more tests, to get enough symptoms to proceed further.

Quote:

Try this:
Start>Run, type msconfig, go to the services tab, and make sure Windows Audio is enabled there.
Make sure to apply, if you enable it.

[xibo]

Quote: Originally Posted by Macho Moron

One question : Vista or XP?

If it's Vista, you deserve to be punished.

Why is that? Because XP will try to write gigabytes of memory onto the hard drive to make it use more battery power and also take longer then using memory like it s supposed to be ... taking even more battery power?

furthermore vista ships with drivers for more recent hardware then xp...

EDIT: dxdiag only works if the hardware is successfully installed, which requires to know what hardware it is in first line

[Macho Moron]

Quote: Originally Posted by xibo

Why is that? Because XP will try to write gigabytes of memory onto the hard drive to make it use more battery power and also take longer then using memory like it s supposed to be ... taking even more battery power?

Let's just say that I have my own reasons, ok? this won't help Poe much anyway.

Quote: Originally Posted by xibo

furthermore vista ships with drivers for more recent hardware then xp...

Uh-huh... which is gay, since it's always best to look for latest drivers on the web and get them.

Quote: Originally Posted by xibo

EDIT: dxdiag only works if the hardware is successfully installed, which requires to know what hardware it is in first line

Obviously, if it doesn't work, at least Poe will post saying so. I lack info in this case anyway.

[xibo]

Spoiler for offtopic

Quote: Originally Posted by Macho Moron

Let's just say that I have my own reasons, ok? this won't help Poe much anyway.

of cause everyone has his own reasons for using an operating system, hardware, browser, text editor, ... gaa i even saw people being fan ( like in cooler ) religious. but then, why does he deserve to be punished if he uses vista?

Quote:

Uh-huh... which is gay, since it's always best to look for latest drivers on the web and get them.

dunno, i can t remember finding a driver for my former computer's sound blaster live card anywhere on the creative page, and currently i can t get a vista driver for my rs232 controller either

Quote:

Obviously, if it doesn't work, at least Poe will post saying so. I lack info in this case anyway.

there s a way to obtain the hardware identifiers under windows, just like lspci does on linux. i've been not using windows for anything more then playing games the last >5 years and forgot it though.
the recent programs that displayed the hardware were programmed lazy and used DX's ( or even worse .net's ) functions ( because it s easier and you usually are using some dx or dotnet components already anyway ) to obtain a list of hardware instead of the win32 ones, and DX/dotnet functions only return the names like they are displayed in the hardware manager

[Poetic]

so.... from my understanding, the linux boot disc seems to be the most promising?

[xibo]

probaly - unless you have someone around who is grokked of windows.
you can get linux boot cds from any distributor's homepage ( e.g. [Only registered users can see links. ] ), it doesn t need to be new or something since you re only querrying device identifiers which is a future that was introduced into linux (linux kernel version - not distribution) 2.0 (around 1995). if you don t know what your architecture is then you have x86 ( pentium/athlon/k6/k5/cyrix series proccessors and anything with 86 at its end )

[lycanbryan]

Quote: Originally Posted by xibo

Why is that? Because XP will try to write gigabytes of memory onto the hard drive to make it use more battery power and also take longer then using memory like it s supposed to be ... taking even more battery power?

furthermore vista ships with drivers for more recent hardware then xp...

EDIT: dxdiag only works if the hardware is successfully installed, which requires to know what hardware it is in first line

In my opinion Vista stinks!!! Not only it is a protection freak... but also displays "Please contact your system administrator" even though you are your own system administrator...

even if you are admin... the OS ask way too many question as if you are a total idiot..

Vista can't run that many games too...

I personally recommend Windows XP or the new XP Nemesis ^^

It is efficient hardware wise to the hardware today.. and it can even run on a low spec computer/laptop like mine ( a 1995 DELL Model ~ 233MhZ ~128RAM ~20G Hard drive ~16MB video ~son on and so fort )

[xibo]

>.>'

someone insulting my beloved vistan?

first off, system administrator != someone logged in with super user access rights.

next, vista CAN run many games. it's only games that use DIRECT3D and their developers are too lazy to patch to d3d10 that can t be run. the D3D incompatibility is actually a feature and not a bug. rewriting an api every 10 years is certainly nothing bad.

and about security, if i spam handle-fdisk on your XP machine you will have lost your partition table and any log files as your partitions are gone and the halt or some pointless interrupt instruction crashed windows long before your firewall can even popup a warning you are being portscanned because of windows xp's aah how so efficent memory management will have swapped the firewall's data on the partition that is no more -.-
and i don t even need to ask whether i can cause handle doom like i could do in NT or OS/2 because XP is just a enhanced version of 1988's OS2.
See why complete rewrites with API changes that eventually break compatibility are important in order to get rid of in-the-meantime-not-wanted-any-more-features?

And it's no way efficent to new hardware as in 64 bit mode it's size type is internally converted to a 32 bit integer in alot of functions even after tons of windows updates and service packs. Also is XP's memory management so incredibly swap oriented it s a pain, and it has crappy page sizes, too.